| /linux/drivers/accessibility/speakup/ |
| H A D | i18n.h | 57 MSG_START, /* A little confusing, given our convention. */
58 MSG_END, /* A little confusing, given our convention. */
|
| /linux/fs/smb/client/ |
| H A D | xattr.c | 30 * confusing users and using the 20+ year old term 'cifs' when it is no longer
459 * confusing users and using the 20 year old term 'cifs' when it is no
493 * confusing users and using the 20 year old term 'cifs' when it is no
513 * confusing users and using the 20 year old term 'cifs' when it is no
|
| /linux/arch/mips/include/asm/mach-malta/ |
| H A D | mach-gt64120.h | 7 * defines won't be confusing in the source code.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 57 define a color without the luminance component Y. It is very confusing
150 mix of different standards also led to very confusing naming conventions
|
| /linux/arch/arm/mach-omap2/ |
| H A D | powerdomains2xxx_3xxx_data.c | 12 * The names for the DSP/IVA2 powerdomains are confusing.
|
| /linux/Documentation/networking/ |
| H A D | x25.rst | 28 Just when you thought that it could not become more confusing, another
|
| H A D | fib_trie.rst | 58 as the opposite of "empty", which might be a tad confusing.)
|
| /linux/tools/testing/selftests/x86/ |
| H A D | sysret_ss_attrs.c | 82 * can be a confusing failure because the SS *selector* in main()
|
| /linux/lib/kunit/ |
| H A D | Kconfig | 35 pass. If this conflicts with your test infrastrcture (or is confusing
|
| /linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_backlight_regs.h | 80 * like the normal CTL from gen4 and earlier. Hooray for confusing naming. */
|
| /linux/tools/perf/Documentation/ |
| H A D | callchain-overhead-calculation.txt | 16 It might be confusing that the sum of all the 'children' overhead
|
| /linux/Documentation/admin-guide/aoe/ |
| H A D | aoe.rst | 42 confusing when an AoE device is not present the first time the a
|
| /linux/Documentation/locking/ |
| H A D | locktorture.rst | 98 in order to avoid confusing boot-time code with CPUs
|
| /linux/fs/xfs/ |
| H A D | xfs_buf_mem.c | 42 * confusing lockdep.
|
| /linux/mm/kmsan/ |
| H A D | report.c | 64 * description can be confusing.
|
| /linux/tools/perf/trace/beauty/include/uapi/linux/ |
| H A D | fcntl.h | 99 * The concept of process and threads in userland and the kernel is a confusing
|
| /linux/Documentation/i2c/ |
| H A D | i2c-sysfs.rst | 99 This may be a confusing part for people who only know about the physical I2C
107 instead of renaming or mapping them, so that it may be less confusing to other
|
| /linux/arch/arm/boot/dts/gemini/ |
| H A D | gemini-sl93512r.dts | 160 * on 18. (Confusing.)
|
| /linux/drivers/net/wireless/ath/carl9170/ |
| H A D | fwcmd.h | 170 * (This is can be a bit confusing, especially
|
| /linux/include/uapi/linux/ |
| H A D | fcntl.h | 99 * The concept of process and threads in userland and the kernel is a confusing
|
| /linux/tools/testing/selftests/pidfd/ |
| H A D | pidfd_getfd_test.c | 260 * confusing. in TEST_F()
|
| /linux/Documentation/input/ |
| H A D | gameport-programming.rst | 94 The only confusing thing here is the fuzz value. Best determined by
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | test_xdp_vlan.sh | |
| /linux/Documentation/gpu/rfc/ |
| H A D | i915_scheduler.rst | 98 the legacy bonding uAPI is quite confusing and not intuitive at all. Furthermore
|
| /linux/drivers/ata/ |
| H A D | pata_hpt3x3.c | 5 * Was pata_hpt34x but the naming was confusing as it supported the
|