| /Linux-v4.19/Documentation/process/ |
| D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
18 companies. If you sign purchase orders or you have any clue about the
19 budget of your group, you're almost certainly not a kernel manager.
20 These suggestions may or may not apply to you.
42 particular, if somebody tells you "choose (a) or (b), we really need you
43 to decide on this", you're in trouble as a manager. The people you
44 manage had better know the details better than you, so if they come to
45 you for a technical decision, you're screwed. You're clearly not
48 (Corollary:if the people you manage don't know the details better than
49 you, you're also screwed, although for a totally different reason.
[all …]
|
| D | maintainer-pgp-guide.rst | 66 Your distro should already have GnuPG installed by default, you just
67 need to verify that you are using version 2.x and not the legacy 1.4
73 If you see ``gpg (GnuPG) 1.4.x``, then you are using GnuPG v.1. Try the
74 ``gpg2`` command (if you don't have it, you may need to install the
79 If you see ``gpg (GnuPG) 2.x.x``, then you are good to go. This guide
80 will assume you have the version 2.2 of GnuPG (or later). If you are
82 not work, and you should consider installing the latest 2.2 version of
86 If you have both ``gpg`` and ``gpg2`` commands, you should make sure you
98 you use the ``gpg`` command and run in the background with the purpose
99 of caching the private key passphrase. There are two options you should
[all …]
|
| D | 6.Followthrough.rst | 6 At this point, you have followed the guidelines given so far and, with the
28 process. Life can be made much easier, though, if you keep a few things in
31 - If you have explained your patch well, reviewers will understand its
32 value and why you went to the trouble of writing it. But that value
35 Many of the changes you may be asked to make - from coding style tweaks
42 they see the same mistakes being made over and over again. If you get a
45 the people, and code reviewers are not attacking you personally.
54 What all of this comes down to is that, when reviewers send you comments,
55 you need to pay attention to the technical observations that they are
57 from happening. When you get review comments on a patch, take the time to
[all …]
|
| /Linux-v4.19/drivers/hwmon/ |
| D | Kconfig | 10 Hardware monitoring devices let you monitor the hardware health
14 control the speed of the fans. If you want this support you
18 To find out which specific driver(s) you need, use the
33 Say Y here if you want the I2C chip drivers to produce a bunch of
34 debug messages to the system log. Select this if you are having
44 If you say yes here you get support for the thermal sensor part
56 If you say yes here you get support for the sensor part of the first
71 If you say yes here you get support for the sensor part of the
85 If you say yes here you get support for the Analog Devices
95 If you say yes here you get support for the Analog Devices
[all …]
|
| /Linux-v4.19/drivers/hwmon/pmbus/ |
| D | Kconfig | 10 Say yes here if you want to enable PMBus support.
21 If you say yes here you get hardware monitoring support for generic
33 If you say yes here you get hardware monitoring support for Analog
44 If you say yes here you get hardware monitoring support for the IBM
54 If you say yes here you get hardware monitoring support for the
64 If you say yes here you get hardware monitoring support for National
74 If you say yes here you get hardware monitoring support for Linear
85 If you say yes here you get regulator support for Linear
92 If you say yes here you get hardware monitoring support for Linear
102 If you say yes here you get hardware monitoring support for Maxim
[all …]
|
| /Linux-v4.19/drivers/block/paride/ |
| D | Kconfig | 17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
33 connected through a parallel port. If you chose to build PARIDE
34 support into your kernel, you may answer Y here to build in the
35 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
40 you have such a CD-ROM drive, you should also say Y or M to "ISO
49 connected through a parallel port. If you chose to build PARIDE
50 support into your kernel, you may answer Y here to build in the
51 parallel port ATAPI disk driver, otherwise you should answer M
[all …]
|
| /Linux-v4.19/drivers/rtc/ |
| D | Kconfig | 18 Generic RTC class support. If you say yes here, you will
28 If you say yes here, the system time (wall clock) will be set using
50 If the clock you specify here is not battery backed, it may still
59 If you say yes here, the system time (wall clock) will be stored
95 Say yes here if you want to use your RTCs using sysfs interfaces,
105 Say yes here if you want to use your system clock RTC through
117 Say yes here if you want to use your RTCs using the /dev
124 versions of "udev" are known to set up the symlink for you.
138 only if you know that you really need it.
143 If you say yes here you get support for the
[all …]
|
| /Linux-v4.19/drivers/w1/slaves/ |
| D | Kconfig | 10 Say Y here if you want to connect 1-wire thermal sensors to your
16 Say Y here if you want to connect 1-wire
22 Say Y or M here if you want to use a DS2405 1-wire
30 Say Y here if you want to use a 1-wire
46 Say Y here if you want to use a 1-wire
53 Say Y or M here if you want to use a 1-wire
61 If you enable this you can read the counter values available
65 Say Y here if you want to use a 1-wire
71 Say Y here if you want to use a 1-wire
79 Say Y here if you want to use a 1-wire
[all …]
|
| /Linux-v4.19/arch/arm/mach-orion5x/ |
| D | Kconfig | 27 Say 'Y' here if you want your kernel to support the
34 Say 'Y' here if you want your kernel to support the
41 Say 'Y' here if you want your kernel to support the
49 Say 'Y' here if you want your kernel to support the Marvell
56 Say 'Y' here if you want your kernel to support the
63 Say 'Y' here if you want your kernel to support the
69 Say 'Y' here if you want your kernel to support the
75 Say 'Y' here if you want your kernel to support the
82 Say 'Y' here if you want your kernel to support the
90 Say 'Y' here if you want your kernel to support the
[all …]
|
| /Linux-v4.19/arch/arm/mach-ep93xx/ |
| D | Kconfig | 21 Say 'Y' here if you want your kernel to support the ADS
28 Say 'Y' here if you want your kernel to support the
38 Say 'Y' here if you want your kernel to support the Cirrus
45 Say 'Y' here if you want your kernel to support the Cirrus
52 Say 'Y' here if you want your kernel to support the Cirrus
59 Say 'Y' here if you want your kernel to support the Cirrus
66 Say 'Y' here if you want your kernel to support the Cirrus
73 Say 'Y' here if you want your kernel to support the Cirrus
80 Say 'Y' here if you want your kernel to support the Cirrus
87 Say 'Y' here if you want your kernel to support the Cirrus
[all …]
|
| /Linux-v4.19/drivers/media/dvb-frontends/ |
| D | Kconfig | 12 A DVB-S/S2/DSS Multistandard demodulator. Say Y when you want
21 demodulator. Say Y when you want to support this tuner.
29 Say Y when you want to support these frontends.
38 Say Y when you want to support these frontends.
54 Say Y when you want to support these frontends.
63 Say Y when you want to support these frontends.
71 Say Y when you want to support this frontend.
83 Say Y when you want to support this frontend.
92 Say Y when you want to support this tuner.
102 Say Y when you want to support this frontend.
[all …]
|
| /Linux-v4.19/fs/jbd2/ |
| D | Kconfig | 13 If you are using ext4 or OCFS2, you need to say Y here.
14 If you are not using ext4 or OCFS2 then you will
18 called jbd2. If you are compiling ext4 or OCFS2 into the kernel,
19 you cannot compile this code as a module.
25 If you are using the ext4 journaled file system (or
27 allows you to enable debugging output while the system is running,
28 in order to help track down any problems you are having.
31 If you select Y here, then you will be able to turn on debugging
|
| /Linux-v4.19/drivers/thermal/ti-soc-thermal/ |
| D | Kconfig | 4 If you say yes here you get support for the Texas Instruments
15 If you say yes here you want to get support for generic thermal
26 If you say yes here you get thermal support for the Texas Instruments
41 If you say yes here you get thermal support for the Texas Instruments
55 If you say yes here you get thermal support for the Texas Instruments
67 If you say yes here you get thermal support for the Texas Instruments
|
| /Linux-v4.19/drivers/staging/olpc_dcon/ |
| D | Kconfig | 14 This controller is only available on OLPC platforms. Unless you have
15 one of these platforms, you will want to say 'N'.
23 communicates with the DCON using model-specific code. If you
24 have an XO-1 (or if you're unsure what model you have), you should
33 communicates with the DCON using model-specific code. If you
34 have an XO-1.5 (or if you're unsure what model you have), you
|
| /Linux-v4.19/drivers/iio/temperature/ |
| D | Kconfig | 12 If you say yes here you get support for the Maxim series of
40 If you say yes here you get support for the Melexis
51 If you say yes here you get support for the Melexis
62 If you say yes here you get support for the Texas Instruments
72 If you say yes here you get support for the Texas Instruments
83 If you say yes here you get support for the Measurement Specialties
94 If you say yes here you get support for the Measurement Specialties
|
| /Linux-v4.19/drivers/pps/clients/ |
| D | Kconfig | 10 If you say yes here you get support for a PPS debugging client
20 If you say yes here you get support for a PPS source connected
27 If you say yes here you get support for a PPS source connected
33 If you say yes here you get support for a PPS source using
34 GPIO. To be useful you must also register a platform device
|
| /Linux-v4.19/Documentation/hid/ |
| D | uhid.txt | 18 dynamically so you need to rely on udev (or similar) to create the device node.
21 If a new device is detected by your HID I/O Driver and you want to register this
22 device with the HID subsystem, then you need to open /dev/uhid once for each
23 device you want to register. All further communication is done by read()'ing or
41 If you want to handle multiple events in a single syscall, then use vectored
47 The first thing you should do is sending an UHID_CREATE2 event. This will
51 That is, you might put your device asleep unless you receive the UHID_OPEN
52 event. If you receive the UHID_OPEN event, you should start I/O. If the last
53 user closes the HID device, you will receive an UHID_CLOSE event. This may be
55 reference-counting in user-space. That is, you will never receive multiple
[all …]
|
| /Linux-v4.19/fs/nls/ |
| D | Kconfig | 34 If you specify a wrong value, it will use the built-in NLS;
45 codepage if you want to be able to read/write these filenames on
48 say Y here if you want to include the DOS codepage that is used in
57 codepage if you want to be able to read/write these filenames on
60 say Y here if you want to include the DOS codepage that is used for
69 codepage if you want to be able to read/write these filenames on
72 say Y here if you want to include the DOS codepage that is used
82 codepage if you want to be able to read/write these filenames on
85 say Y here if you want to include the DOS codepage that is used for
98 codepage if you want to be able to read/write these filenames on
[all …]
|
| /Linux-v4.19/Documentation/networking/ |
| D | arcnet.txt | 3 and cabling information if you're like many of us and didn't happen to get a
15 The point is: I REALLY REALLY REALLY REALLY REALLY want to hear from you if
16 you test this and get it working. Or if you don't. Or anything.
31 If you don't e-mail me about your success/failure soon, I may be forced to
35 If you think so, why not flame me in a quick little e-mail? Please also
36 include the type of card(s) you're using, software, size of network, and
85 Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
98 one you'll want to use with ARCnet cards) from
101 versions are available on my WWW page, or via e-mail if you don't have WWW
108 All you will need to do in order to install the driver is:
[all …]
|
| /Linux-v4.19/Documentation/media/kapi/ |
| D | v4l2-dev.rst | 19 If you embed it in a larger struct, then you must set the ``release()``
52 - :c:type:`video_device`->ioctl_ops: if you use the :c:type:`v4l2_ioctl_ops`
62 - :c:type:`video_device`->lock: leave to ``NULL`` if you want to do all the
63 locking in the driver. Otherwise you give it a pointer to a struct
83 in :c:type:`v4l2_device`. If you want to have a separate priority state per
84 (group of) device node(s), then you can point it to your own struct
87 - :c:type:`video_device`->dev_parent: you only set this if v4l2_device was
96 struct :c:type:`video_device` is initialized you **do** know which parent
97 PCI device to use and so you set ``dev_device`` to the correct PCI device.
99 If you use :c:type:`v4l2_ioctl_ops`, then you should set
[all …]
|
| /Linux-v4.19/drivers/media/rc/ |
| D | Kconfig | 10 Enable this option if you have a video capture board even
11 if you don't need IR, as otherwise, you may not be able to
14 Say Y when you have a TV or an IR device.
52 Enable this option if you have IR with NEC protocol, and
61 Enable this option if you have IR with RC-5 protocol, and
70 Enable this option if you have an infrared remote control which
71 uses the RC6 protocol, and you need software decoding support.
79 Enable this option if you have an infrared remote control which
80 uses the JVC protocol, and you need software decoding support.
88 Enable this option if you have an infrared remote control which
[all …]
|
| /Linux-v4.19/Documentation/locking/ |
| D | spinlocks.txt | 25 The above is usually pretty simple (you usually need and want only one
28 sequences that you _know_ need to be split up: avoid it at all cost if you
31 This is really the only really hard part about spinlocks: once you start
32 using spinlocks they tend to expand to areas you might not have noticed
33 before, because you have to make sure the spinlocks correctly protect the
38 NOTE! The spin-lock is safe only when you _also_ use the lock itself
47 If your data accesses have a very natural pattern where you usually tend
54 simple spinlocks. Unless the reader critical section is long, you
79 Also, you cannot "upgrade" a read-lock to a write-lock, so if you at _any_
80 time need to do any changes (even if you don't do it every time), you have
[all …]
|
| /Linux-v4.19/drivers/gpu/drm/exynos/ |
| D | Kconfig | 8 Choose this option if you have a Samsung SoC EXYNOS chipset.
25 Choose this option if you want to use Exynos FIMD for DRM.
30 Choose this option if you want to use Exynos5433 DECON for DRM.
36 Choose this option if you want to use Exynos DECON for DRM.
41 Choose this option if you want to use Exynos Mixer for DRM.
46 Choose this option if you want to use Exynos VIDI for DRM.
81 Choose this option if you want to use Exynos HDMI for DRM.
87 Choose this option if you want to use Exynos MIC for DRM.
96 Choose this option if you want to use Exynos G2D for DRM.
105 Choose this option if you want to use Exynos FIMC for DRM.
[all …]
|
| /Linux-v4.19/drivers/hsi/clients/ |
| D | Kconfig | 11 Say Y here if you want to add support for the modem on Nokia
20 If you say Y here, you will enable the CMT speech protocol used
21 by Nokia modems. If you say M the protocol will be available as
30 If you say Y here, you will enable the SSI protocol aka McSAAB.
38 If you say Y here, you will enable the HSI/SSI character driver.
|
| /Linux-v4.19/arch/nios2/ |
| D | Kconfig | 63 keeps in the memory allocator. If you need to allocate very large
64 blocks of physically contiguous memory, then you may need to
90 emulated in software if you say Y here, which has a performance
105 pass arguments to the kernel. For these platforms, you can supply
107 other cases you can specify kernel args so that you don't have
132 Say N if you are unsure.
138 This option allows you to set the link address offset of the zImage.
139 This can be useful if you are on a board which has a small amount of
156 This option allows you to set the virtual address of the kernel MMU region.
158 Say N here unless you know what you are doing.
[all …]
|
