Home
last modified time | relevance | path

Searched full:confusing (Results 1 – 25 of 348) sorted by relevance

12345678910>>...14

/kernel/linux/linux-5.10/drivers/accessibility/speakup/
Di18n.h51 MSG_START, /* A little confusing, given our convention. */
52 MSG_END, /* A little confusing, given our convention. */
/kernel/linux/linux-6.6/drivers/accessibility/speakup/
Di18n.h57 MSG_START, /* A little confusing, given our convention. */
58 MSG_END, /* A little confusing, given our convention. */
/kernel/linux/linux-6.6/fs/smb/client/
Dxattr.c30 * confusing users and using the 20+ year old term 'cifs' when it is no longer
433 * confusing users and using the 20 year old term 'cifs' when it is no
453 * confusing users and using the 20 year old term 'cifs' when it is no
473 * confusing users and using the 20 year old term 'cifs' when it is no
/kernel/linux/linux-5.10/arch/mips/include/asm/mach-malta/
Dmach-gt64120.h7 * defines won't be confusing in the source code.
/kernel/linux/linux-6.6/arch/mips/include/asm/mach-malta/
Dmach-gt64120.h7 * defines won't be confusing in the source code.
/kernel/linux/linux-5.10/drivers/staging/gdm724x/
DTODO4 - Remove confusing macros (endian, hci_send, sdu_send, rcv_with_cb)
/kernel/linux/linux-6.6/drivers/staging/gdm724x/
DTODO4 - Remove confusing macros (endian, hci_send, sdu_send, rcv_with_cb)
/kernel/linux/linux-6.6/Documentation/filesystems/ext4/
Dbitmaps.rst21 which produces confusing debugfs output.
/kernel/linux/linux-5.10/Documentation/filesystems/ext4/
Dbitmaps.rst21 which produces confusing debugfs output.
/kernel/linux/linux-6.6/drivers/staging/qlge/
DTODO14 queues" is confusing.
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dcolorspaces.rst57 define a color without the luminance component Y. It is very confusing
150 mix of different standards also led to very confusing naming conventions
/kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/
Dcolorspaces.rst57 define a color without the luminance component Y. It is very confusing
150 mix of different standards also led to very confusing naming conventions
/kernel/linux/linux-6.6/arch/arm/mach-omap2/
Dpowerdomains2xxx_3xxx_data.c12 * The names for the DSP/IVA2 powerdomains are confusing.
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dpowerdomains2xxx_3xxx_data.c12 * The names for the DSP/IVA2 powerdomains are confusing.
/kernel/linux/linux-5.10/Documentation/networking/
Dx25.rst30 Just when you thought that it could not become more confusing, another
/kernel/linux/linux-6.6/Documentation/networking/
Dx25.rst28 Just when you thought that it could not become more confusing, another
/kernel/linux/linux-5.10/fs/cifs/
Dxattr.c41 * confusing users and using the 20+ year old term 'cifs' when it is no longer
461 * confusing users and using the 20 year old term 'cifs' when it is no
481 * confusing users and using the 20 year old term 'cifs' when it is no
/kernel/linux/linux-5.10/drivers/staging/qlge/
DTODO14 queues" is confusing.
/kernel/linux/linux-5.10/fs/
Dcompat_binfmt_elf.c128 * might make some debugging less confusing not to duplicate them.
/kernel/linux/linux-6.6/tools/testing/selftests/x86/
Dsysret_ss_attrs.c82 * can be a confusing failure because the SS *selector* in main()
/kernel/linux/linux-5.10/tools/testing/selftests/x86/
Dsysret_ss_attrs.c82 * can be a confusing failure because the SS *selector* in main()
/kernel/linux/linux-6.6/fs/
Dcompat_binfmt_elf.c133 * might make some debugging less confusing not to duplicate them.
/kernel/linux/linux-6.6/drivers/gpu/drm/i915/display/
Dintel_backlight_regs.h80 * like the normal CTL from gen4 and earlier. Hooray for confusing naming. */
/kernel/linux/linux-6.6/tools/perf/Documentation/
Dcallchain-overhead-calculation.txt15 It might be confusing that the sum of all the 'children' overhead
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dcallchain-overhead-calculation.txt15 It might be confusing that the sum of all the 'children' overhead

12345678910>>...14