Home
last modified time | relevance | path

Searched refs:should (Results 1 – 25 of 82) sorted by relevance

1234

/linux-4.19.296/drivers/memstick/
DKconfig10 If you want MemoryStick support, you should say Y here and also
18 This is an option for use by developers; most people should
/linux-4.19.296/drivers/memstick/core/
DKconfig17 a MemoryStick card for rootfs. Most people should say N here.
26 support should say Y or M here.
/linux-4.19.296/fs/kernfs/
DKconfig2 # KERNFS should be selected by its users
/linux-4.19.296/drivers/media/v4l2-core/
Dvideobuf-vmalloc.c33 #define MAGIC_CHECK(is, should) \ argument
34 if (unlikely((is) != (should))) { \
36 is, should); \
Dvideobuf-dma-contig.c34 #define MAGIC_CHECK(is, should) \ argument
35 if (unlikely((is) != (should))) { \
36 pr_err("magic mismatch: %x expected %x\n", (is), (should)); \
/linux-4.19.296/drivers/ntb/hw/idt/
DKconfig8 exposes it NT-functions correctly. It should be done by either proper
25 techniques like BIOS using SMBus interface or EEPROM should be
/linux-4.19.296/drivers/isdn/capi/
DKconfig15 applications via /dev/capi20. Applications should use the
16 standardized libcapi20 to access this functionality. You should say
/linux-4.19.296/drivers/of/unittest-data/
Doverlay_bad_phandle.dts7 // This label should cause an error when the overlay
Doverlay_bad_symbol.dts7 // This label should cause an error when the overlay
/linux-4.19.296/fs/configfs/
DKconfig10 Both sysfs and configfs can and should exist together on the
/linux-4.19.296/drivers/base/
DKconfig13 This should not be used today, because usual systems create
81 should only be needed if you have an updated firmware source.
83 Firmware should not be being built as part of kernel, these days
84 you should always prevent this and say Y here. There are only two
96 Drivers should "select" this option if they desire to use the
149 unusable. You should say N here unless you are explicitly looking to
/linux-4.19.296/fs/exofs/
DKconfig.ore4 # for every ORE user we do it like this. Any user should add itself here
/linux-4.19.296/drivers/media/rc/keymaps/
DKconfig10 tables on userspace, you should disable it.
/linux-4.19.296/drivers/parport/
DKconfig46 You should say Y here if you have a PC-style parallel port. All
48 parallel ports. PA-RISC owners should only say Y here if they
61 serial ports. You should say Y or M here. If you say M, the module
151 should not interfere with the networking functions of the chip.
DTODO-parport13 bits when they have something to say. We should read out and deal
/linux-4.19.296/fs/proc/
DKconfig21 That location should be /proc. A command such as "mount -t proc proc
29 programs depend on this, so everyone should say Y here.
77 As it is generally a good thing, you should say Y here unless
/linux-4.19.296/drivers/base/regmap/
DKconfig4 # subsystems should select the appropriate symbols.
/linux-4.19.296/drivers/misc/cb710/
DKconfig19 This is an option for use by developers; most people should
/linux-4.19.296/drivers/pci/endpoint/
DKconfig13 endpoint. This should be enabled if the platform has a PCI
/linux-4.19.296/drivers/virt/vboxguest/
DKconfig13 If you enable this driver you should also enable the VBOXVIDEO option.
/linux-4.19.296/fs/fat/
DKconfig51 partitions, you should use the VFAT file system (say Y to "VFAT fs
82 This option should be set to the codepage of your FAT filesystems.
92 like FAT to use. It should probably match the character set
/linux-4.19.296/drivers/cpuidle/
DKconfig13 If you're using an ACPI-enabled platform, you should say Y here.
/linux-4.19.296/fs/reiserfs/
DKconfig42 everyone should say N.
53 reiserfs or tracing problems should say N.
/linux-4.19.296/fs/befs/
DKconfig13 If you use this filesystem, you should also say Y to at least one
/linux-4.19.296/fs/bfs/
DKconfig9 partition. You should say Y if you want to read or write the files

1234