| /linux/Documentation/process/ |
| H A D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
19 companies. If you sign purchase orders or you have any clue about the
20 budget of your group, you're almost certainly not a kernel manager.
21 These suggestions may or may not apply to you.
43 particular, if somebody tells you "choose (a) or (b), we really need you
44 to decide on this", you're in trouble as a manager. The people you
45 manage had better know the details better than you, so if they come to
46 you for a technical decision, you're screwed. You're clearly not
49 (Corollary:if the people you manage don't know the details better than
50 you, you're also screwed, although for a totally different reason.
[all …]
|
| H A D | maintainer-pgp-guide.rst | 68 Your distro should already have GnuPG installed by default, you just
69 need to verify that you are using a reasonably recent version of it.
74 If you have version 2.4 or above, then you are good to go. If you have
75 an earlier version, then you are using a release of GnuPG that is no
82 you use the ``gpg`` command and run in the background with the purpose
83 of caching the private key passphrase. There are two options you should
86 - ``default-cache-ttl`` (seconds): If you use the same key again before
89 - ``max-cache-ttl`` (seconds): Regardless of how recently you've used
91 countdown expires, you'll have to enter the passphrase again. The
94 If you find either of these defaults too short (or too long), you can
[all …]
|
| H A 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.
61 What all of this comes down to is that, when reviewers send you comments,
62 you need to pay attention to the technical observations that they are
64 from happening. When you get review comments on a patch, take the time to
[all …]
|
| H A D | backporting.rst | 21 techniques you can use to make the process smoother and increase your
30 Sometimes the patch you are backporting already exists as a git commit,
31 in which case you just cherry-pick it directly using
33 often does for the Linux kernel, you will need to apply it to a tree
36 If you've ever used ``git am``, you probably already know that it is
38 fact, you've probably had nightmares about ``.rej`` files and trying to
44 you resolve conflicts with the help of git and any other conflict
45 resolution tools you might prefer to use. For example, if you want to
46 apply a patch that just arrived on LKML to an older stable kernel, you
63 If you are using `b4`_. and you are applying the patch directly from an
[all …]
|
| H A D | applying-patches.rst | 12 manually, you'll almost certainly want to look at using Git instead.
17 will explain this to you.
31 To correctly apply a patch you need to know what base it was generated from
52 unlabeled patch was generated against) you should change into your kernel
58 So, if you applied a patch like this::
78 If you just want to be able to follow the examples below and don't want to
79 know of more than one way to use patch, then you can stop reading this
87 If your patch file is compressed with gzip or xz and you don't want to
88 uncompress it before applying it, then you can feed it to patch like this
94 If you wish to uncompress the patch file by hand first before applying it
[all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 19 Generic RTC class support. If you say yes here, you will
29 If you say yes here, the system time (wall clock) will be set using
48 If the clock you specify here is not battery backed, it may still
57 If you say yes here, the system time (wall clock) will be stored
102 Say yes here if you want to use your RTCs using sysfs interfaces,
112 Say yes here if you want to use your system clock RTC through
124 Say yes here if you want to use your RTCs using the /dev
131 versions of "udev" are known to set up the symlink for you.
145 only if you know that you really need it.
150 If you say yes here you get support for the
[all …]
|
| /linux/drivers/hwmon/ |
| H A D | Kconfig | 11 Hardware monitoring devices let you monitor the hardware health
15 control the speed of the fans. If you want this support you
19 To find out which specific driver(s) you need, use the
34 Say Y here if you want the I2C chip drivers to produce a bunch of
35 debug messages to the system log. Select this if you are having
45 If you say yes here you get support for the sensor part of the first
60 If you say yes here you get support for the sensor part of the
74 If you say yes here you get support for the thermal, voltage,
82 If you say yes here you get support for the Analog Devices
92 If you say yes here you get support for the Analog Devices
[all …]
|
| /linux/drivers/w1/slaves/ |
| H A D | Kconfig | 11 Say Y here if you want to connect 1-wire thermal sensors to your
17 Say Y here if you want to connect 1-wire
23 Say Y or M here if you want to use a DS2405 1-wire
31 Say Y here if you want to use a 1-wire
47 Say Y here if you want to use a 1-wire
54 Say Y or M here if you want to use a 1-wire
62 If you enable this you can read the counter values available
66 Say Y here if you want to use a 1-wire
72 Say Y here if you want to use a 1-wire
80 Say Y here if you want to use a 1-wire 256bit EEPROM
[all …]
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | Kconfig | 20 Say Y when you want to support this frontend.
29 Say Y when you want to support these frontends.
36 A DVB-S/S2/DSS Multistandard demodulator. Say Y when you want
45 demodulator. Say Y when you want to support this tuner.
53 Say Y when you want to support these frontends.
62 Say Y when you want to support these frontends.
78 Say Y when you want to support these frontends.
90 Say Y when you want to support this frontend.
98 Say Y when you want to support this frontend.
106 Say Y when you want to support this frontend.
[all …]
|
| /linux/drivers/iio/temperature/ |
| H A D | Kconfig | 11 Say Y here if you want to build support for the Azoteq IQS620AT
34 If you say yes here you get support for the Maxim series of
61 If you say yes here you get support for the Melexis
72 If you say yes here you get support for the Melexis
84 If you say yes here you get support for the Melexis
97 If you say yes here you get support for the Texas Instruments
107 If you say yes here you get support for the Texas Instruments
117 If you say yes here you get support for the Texas Instruments
128 If you say yes here you get support for the Measurement Specialties
139 If you say yes here you get support for the Measurement Specialties
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | journalling.rst | 12 how you decide to allocate the physical media on which the journal
16 journal_t is a typedef for a struct pointer, so when you are finally
17 finished make sure you call jbd2_journal_destroy() on it to free up
20 Once you have got your journal_t object you need to 'mount' or load the
23 When loading the journal you must call jbd2_journal_load() to process
30 jbd2_journal_skip_recovery() for you if it detects any outstanding
35 Now you can go ahead and start modifying the underlying filesystem.
39 by wrapping them into transactions. Additionally you also need to wrap
41 so it knows what the modifications you are actually making are. To do
45 which indicates the end of a transaction are nestable calls, so you can
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | quickly-build-trimmed-linux.rst | 14 *[If you are new to compiling Linux, ignore this TLDR and head over to the next
18 which might be relevant for you.]*
24 you then use to configure, build and install your own kernel::
29 # Hint: if you want to apply patches, do it at this point. See below for details.
32 # Hint: at this point you might want to adjust the build configuration; you'll
33 # have to, if you are running Debian. See below for details.
40 If you later want to build a newer mainline snapshot, use these commands::
44 # Note: the next command will discard any changes you did to the code:
46 # Reminder: if you want to (re)apply patches, do it at this point.
47 # Reminder: you might want to add or modify a build tag at this point.
[all …]
|
| H A D | reporting-issues.rst | 11 Are you facing a regression with vanilla kernels from the same stable or
15 you don't find any, install `the latest release from that series
25 search the `LKML <https://lore.kernel.org/lkml/>`_ and the web, too. If you
29 The issue was fixed there, but you would like to see it resolved in a still
40 If you are facing multiple issues with the Linux kernel at once, report each
44 to pinpoint the culprit with a bisection; if you succeed, include its
47 Once the report is out, answer any questions that come up and help where you
63 a slightly different order. That's in your interest, to make sure you notice
65 something else. These steps thus help to ensure the time you invest in this
68 * Are you facing an issue with a Linux kernel a hardware or software vendor
[all …]
|
| H A D | verify-bugs-and-bisect-regressions.rst | 20 Note: if you see this note, you are reading the text's source file. You
22 read and navigate this document -- especially when you want to look something
23 up in the reference section, then jump back to where you left off.
31 *[If you are new to building or bisecting Linux, ignore this section and head
38 **In case you want to check if a bug is present in code currently supported by
40 consider the newest Linux kernel you regularly use to be the 'working' kernel.
44 **In case you face a regression**, follow the steps at least till the end of
45 *segment 2*. Then you can submit a preliminary report -- or continue with
56 # * If you are not already running the 'working' kernel, reboot into it.
65 # * Hint: if you used an existing clone, ensure no stale .config is around.
[all …]
|
| H A D | spkguide.txt | 23 interface to Speakup, a Linux Screen Reader. If you need instructions
33 the system is shutdown. This means that if you have obtained Linux
35 of its kernel, you will be able, as a blind person, to install Linux
43 specific synthesizer by default, then all you need to do to use Speakup
52 synthesizers and not others. If you find that this is the case, and
59 synthesizer set, or you would like to use a different synthesizer than
60 the default one, then you may issue the following command at the boot
67 with the keyword for whatever synthesizer you wish to use. The
107 administrator. This will mean that you will hear some, but not all, of
112 Once you have booted the system, and if necessary, have supplied the
[all …]
|
| /linux/Documentation/networking/ |
| H A D | arcnet.rst | 12 and cabling information if you're like many of us and didn't happen to get a
24 The point is: I REALLY REALLY REALLY REALLY REALLY want to hear from you if
25 you test this and get it working. Or if you don't. Or anything.
69 Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
84 one you'll want to use with ARCnet cards) from
87 versions are available on my WWW page, or via e-mail if you don't have WWW
94 All you will need to do in order to install the driver is::
102 If you obtained this ARCnet package as an upgrade to the ARCnet driver in
103 your current kernel, you will need to first copy arcnet.c over the one in
106 You will know the driver is installed properly if you get some ARCnet
[all …]
|
| /linux/fs/nls/ |
| H A D | Kconfig | 35 If you specify a wrong value, it will use the built-in NLS;
46 codepage if you want to be able to read/write these filenames on
49 say Y here if you want to include the DOS codepage that is used in
58 codepage if you want to be able to read/write these filenames on
61 say Y here if you want to include the DOS codepage that is used for
70 codepage if you want to be able to read/write these filenames on
73 say Y here if you want to include the DOS codepage that is used
83 codepage if you want to be able to read/write these filenames on
86 say Y here if you want to include the DOS codepage that is used for
99 codepage if you want to be able to read/write these filenames on
[all …]
|
| /linux/Documentation/hid/ |
| H A D | uhid.rst | 19 dynamically so you need to rely on udev (or similar) to create the device node.
22 If a new device is detected by your HID I/O Driver and you want to register this
23 device with the HID subsystem, then you need to open /dev/uhid once for each
24 device you want to register. All further communication is done by read()'ing or
42 If you want to handle multiple events in a single syscall, then use vectored
48 The first thing you should do is send a UHID_CREATE2 event. This will
52 That is, you might put your device asleep unless you receive the UHID_OPEN
53 event. If you receive the UHID_OPEN event, you should start I/O. If the last
54 user closes the HID device, you will receive a UHID_CLOSE event. This may be
56 reference-counting in user-space. That is, you will never receive multiple
[all …]
|
| /linux/drivers/media/rc/ |
| H A D | Kconfig | 11 Enable this option if you have a video capture board even
12 if you don't need IR, as otherwise, you may not be able to
15 Say Y when you have a TV or an IR device.
50 Enable this option if you have iMON PAD or Antec Veris infrared
51 remote control and you would like to use it with a raw IR
52 receiver, or if you wish to use an encoder to transmit this IR.
59 Enable this option if you have an infrared remote control which
60 uses the JVC protocol, and you need software decoding support.
67 Enable this option if you have a Microsoft Remote Keyboard for
68 Windows Media Center Edition, which you would like to use with
[all …]
|
| /linux/fs/jbd2/ |
| H A D | Kconfig | 12 If you are using ext4 or OCFS2, you need to say Y here.
13 If you are not using ext4 or OCFS2 then you will
17 called jbd2. If you are compiling ext4 or OCFS2 into the kernel,
18 you cannot compile this code as a module.
24 If you are using the ext4 journaled file system (or
26 allows you to enable debugging output while the system is running,
27 in order to help track down any problems you are having.
30 If you select Y here, then you will be able to turn on debugging
|
| /linux/drivers/media/usb/gspca/ |
| H A D | Kconfig | 8 Say Y here if you want to enable selecting webcams based
25 Say Y here if you want support for the Benq DC E300 camera.
34 Say Y here if you want support for cameras based on the Conexant chip.
43 Say Y here if you want support for USB cameras based on the cpia
44 CPiA chip. Note that you need at least version 0.6.4 of libv4l for
54 Say Y here if you want support for the Scopium camera
64 Say Y here if you want support for cameras based on the Etoms chip.
73 Say Y here if you want support for cameras based on the FinePix chip.
82 Say Y here if you want support for cameras based on this Jeilin chip.
91 Say Y here if you want support for cameras based the
[all …]
|
| /linux/net/dsa/ |
| H A D | Kconfig | 14 Say Y if you want to enable support for the hardware switches supported
24 Say Y or M if you want to enable support for switches which don't tag
30 Say Y or M if you want to enable support for tagging frames for
41 Say Y if you want to enable support for tagging frames for the
48 Say Y if you want to enable support for tagging frames for the
58 Say Y if you want to enable support for tagging frames for the
68 Say Y if you want to enable support for tagging frames for the
75 Say Y or M if you want to enable support for tagging frames
81 Say Y or M if you want to enable support for tagging frames for the
91 Say Y or M if you want to enable support for tagging frames for the
[all …]
|
| /linux/drivers/thermal/ti-soc-thermal/ |
| H A D | Kconfig | 5 If you say yes here you get support for the Texas Instruments
16 If you say yes here you want to get support for generic thermal
27 If you say yes here you get thermal support for the Texas Instruments
42 If you say yes here you get thermal support for the Texas Instruments
56 If you say yes here you get thermal support for the Texas Instruments
68 If you say yes here you get thermal support for the Texas Instruments
|
| /linux/drivers/pps/clients/ |
| H A D | Kconfig | 11 If you say yes here you get support for a PPS debugging client
21 If you say yes here you get support for a PPS source connected
28 If you say yes here you get support for a PPS source connected
34 If you say yes here you get support for a PPS source using
35 GPIO. To be useful you must also register a platform device
|
| /linux/drivers/iio/light/ |
| H A D | Kconfig | 17 Say Y here if you want to build a driver for the ACPI0008
29 If you say yes here you get support for the Avago ADJD-S311-CR999
40 Say Y here if you want to build a driver for the Analog Devices
50 Say Y here if you want to build a driver for the Dyna Image AL3000a
60 Say Y here if you want to build a driver for the Dyna Image AL3010
70 Say Y here if you want to build a driver for the Dyna Image AL3320A
81 Say Y here if you want to build support for a Broadcom APDS9160
91 Say Y here if you want to build a driver for the Avago APDS9300
103 If you say Y or M here, you get support for Avago APDS9306
128 If you say yes here you get support for the AMS AS73211
[all …]
|