| /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 | 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/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/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/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/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/drivers/clk/qcom/ |
| H A D | Kconfig | 29 Say Y if you want to support display devices and functionality such as
38 Say Y if you want to use peripheral devices such as UART, SPI,
47 Say Y if you want to use peripheral devices such as USB/PCIe/EDP.
55 Say Y if you want to support camera devices and camera functionality.
64 Say Y if you want to support display devices and functionality such as
74 Say Y if you want to use peripheral devices such as UART, SPI, I2C,
83 Say Y if you want to support graphics controller devices and
92 Say Y if you want to use peripheral devices such as SD/UFS.
100 Say Y if you want to support graphics controller devices and
109 Say Y if you want to support graphics controller devices and
[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/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/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/Documentation/admin-guide/ |
| 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/driver-api/media/ |
| H A D | v4l2-dev.rst | 21 If you embed it in a larger struct, then you must set the ``release()``
54 - :c:type:`video_device`->ioctl_ops: if you use the :c:type:`v4l2_ioctl_ops`
64 - :c:type:`video_device`->lock: leave to ``NULL`` if you want to do all the
65 locking in the driver. Otherwise you give it a pointer to a struct
85 in :c:type:`v4l2_device`. If you want to have a separate priority state per
86 (group of) device node(s), then you can point it to your own struct
89 - :c:type:`video_device`->dev_parent: you only set this if v4l2_device was
98 struct video_device is initialized you **do** know which parent
99 PCI device to use and so you set ``dev_device`` to the correct PCI device.
101 If you use :c:type:`v4l2_ioctl_ops`, then you should set
[all …]
|
| /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/arch/arm/mach-orion5x/ |
| H A D | Kconfig | 28 Say 'Y' here if you want your kernel to support the
36 Say 'Y' here if you want your kernel to support the Marvell
44 Say 'Y' here if you want your kernel to support the
52 Say 'Y' here if you want your kernel to support the
59 Say 'Y' here if you want your kernel to support the
66 Say 'Y' here if you want your kernel to support the
74 Say 'Y' here if you want your kernel to support the
82 Say 'Y' here if you want your kernel to support the
89 Say 'Y' here if you want your kernel to support the
96 Say 'Y' here if you want your kernel to support the
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | idr.rst | 31 the pointer you associated with the ID by calling idr_find()
34 If you need to change the pointer associated with an ID, you can call
42 idr_alloc_u32(). If you need IDs that will not fit in a u32,
43 we will work with you to address your needs.
45 If you need to allocate IDs sequentially, you can use
49 To perform an action on all pointers used by the IDR, you can
55 When you have finished using an IDR, you can call idr_destroy()
57 pointed to from the IDR; if you want to do that, use one of the iterators
63 If you need to take a lock while allocating a new ID from the IDR,
64 you may need to pass a restrictive set of GFP flags, which can lead
[all …]
|
| /linux/Documentation/locking/ |
| H A D | spinlocks.rst | 32 The above is usually pretty simple (you usually need and want only one
35 sequences that you **know** need to be split up: avoid it at all cost if you
38 This is really the only really hard part about spinlocks: once you start
39 using spinlocks they tend to expand to areas you might not have noticed
40 before, because you have to make sure the spinlocks correctly protect the
45 NOTE! The spin-lock is safe only when you **also** use the lock itself
55 If your data accesses have a very natural pattern where you usually tend
62 simple spinlocks. Unless the reader critical section is long, you
87 Also, you cannot "upgrade" a read-lock to a write-lock, so if you at _any_
88 time need to do any changes (even if you don't do it every time), you have
[all …]
|
| /linux/drivers/char/agp/ |
| H A D | Kconfig | 10 If you have an AGP system and you say Y here, it will be possible to
14 If you need more texture memory than you can get with the AGP GART
16 due to kernel allocation issues), you could use PCI accesses
26 You should say Y here if you want to use GLX or DRI.
34 This option gives you AGP support for the GLX component of
37 For the ALi-chipset question, ALi suggests you refer to
49 This option gives you AGP support for the GLX component of
56 This option gives you AGP support for the GLX component of
63 This option gives you AGP support for the GLX component of
74 This option gives you AGP support for the GLX component of X
[all …]
|
| /linux/drivers/hsi/clients/ |
| H A D | Kconfig | 12 Say Y here if you want to add support for the modem on Nokia
21 If you say Y here, you will enable the CMT speech protocol used
22 by Nokia modems. If you say M the protocol will be available as
31 If you say Y here, you will enable the SSI protocol aka McSAAB.
39 If you say Y here, you will enable the HSI/SSI character driver.
|
| /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 wan
[all...] |
| /linux/Documentation/arch/s390/ |
| H A D | 3270.rst | 21 You may have 3270s in-house and not know it. If you're using the
23 the command "DEF GRAF <hex-address>" This paper presumes you will be
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
34 and this Linux-390 3270 driver, you have another way of talking to your
47 WARNING: If you are using 3270 console support, you must rerun the
48 configuration script every time you change the console's address (perhaps
50 you should rerun the configuration script every time your set of 3270s,
55 If you have chosen to make tub3270 a module, you add a line to a
56 configuration file under /etc/modprobe.d/. If you are working on a VM
57 virtual machine, you can use DEF GRAF to define virtual 3270 devices.
[all …]
|
| /linux/drivers/tty/serial/ |
| H A D | Kconfig | 26 This selects the ARM(R) AMBA(R) PrimeCell PL010 UART. If you have
27 an Integrator/AP or Integrator/PP2 platform, or if you have a
37 Say Y here if you wish to use an AMBA PrimeCell UART as the system
41 Even if you say Y here, the currently visible framebuffer console
43 you can alter that using a kernel command line option such as
53 This selects the ARM(R) AMBA(R) PrimeCell PL011 UART. If you have
65 Say Y here if you wish to use an AMBA PrimeCell UART as the system
69 Even if you say Y here, the currently visible framebuffer console
71 you can alter that using a kernel command line option such as
121 If you say Y here, it will be possible to use a serial port as the
[all …]
|
| /linux/fs/fat/ |
| H A D | Kconfig | 8 If you want to use one of the FAT-based file systems (the MS-DOS and
9 VFAT (Windows 95) file systems), then you must say Y or M here
25 If you need to move large files on floppies between a DOS and a
34 fat. Note that if you compile the FAT support as a module, you
42 This allows you to mount MSDOS partitions of your hard drive (unless
44 Linux, you can either use the DOS emulator DOSEMU, described in the
47 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
53 If you have Windows 95 or Windows NT installed on your MSDOS
54 partitions, you should use the VFAT file system (say Y to "VFAT fs
55 support" below), or you will not be able to see the long filenames
[all …]
|