| /linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 7 addition of your own engineering skills, have posted a perfect series of
17 kernel community to ensure that your code is up to the kernel's quality
19 prevent the inclusion of your patches into the mainline.
31 - If you have explained your patch well, reviewers will understand its
48 agendas at the expense of your own. Kernel developers often expect to
55 and requests to factor out some of your code to shared parts of
57 the same. Sometimes this means that the clever hack in your driver
63 making. Do not let their form of expression or your own pride keep that
70 reviewers. If you believe that the reviewer has misunderstood your code,
72 suggested change, describe it and justify your solution to the problem. If
[all …]
|
| H A D | botching-up-ioctls.rst | 46 conversion or worse, fiddle the raw __u64 through your code since that
60 * Have a clear way for userspace to figure out whether your new ioctl or ioctl
73 and reject the ioctl if that's not the case. Otherwise your nice plan for
99 * Have simple testcases for every input validation failure case in your ioctl.
100 Check that the error code matches your expectations. And finally make sure
106 * Make all your ioctls restartable. First X really loves signals and second
108 interrupting your main test suite constantly with signals. Thanks to X's
109 love for signal you'll get an excellent base coverage of all your error
117 killable. GPUs just die and your users won't like you more if you hang their
122 * Have testcases for the really tricky corner cases in your error recovery code
[all …]
|
| H A D | howto.rst | 21 have been told by your manager, "Go write a Linux driver for this
55 documented; do not expect people to adapt to you or your company's way
214 will learn the basics of getting your patch into the Linux kernel tree,
353 One of the best ways to put into practice your hacking skills is by fixing
356 improve your skills, and other developers will be aware of your presence.
404 If multiple people respond to your mail, the CC: list of recipients may
410 Remember to keep the context and the attribution of your replies intact,
411 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
412 add your statements between the individual quoted sections instead of
415 If you add patches to your mail, make sure they are plain readable text
[all …]
|
| H A D | stable-api-nonsense.rst | 6 (all of your questions answered and then some)
30 you get that only if your driver is in the main kernel tree. You also
31 get lots of other good benefits if your driver is in the main kernel
84 Now a number of these issues can be addressed by simply compiling your
95 multiple versions of your module.
172 Simple, get your kernel driver into the main kernel tree (remember we are
173 talking about drivers released under a GPL-compatible license here, if your
174 code doesn't fall under this category, good luck, you are on your own here,
175 you leech). If your driver is in the tree, and a kernel interface changes,
177 place. This ensures that your driver is always buildable, and works over
[all …]
|
| H A D | management-style.rst | 20 budget of your group, you're almost certainly not a kernel manager.
52 your brilliance instead).
61 small one is whether you can fix your decision afterwards. Any decision
97 the first place, and your decision ended up being a big one after
102 people ahead of the fact that your decision is purely preliminary, and
104 your mind, and make people very **aware** of that. And it's much easier
178 .. [#f2] Paul Simon sang "Fifty Ways to Leave Your Lover", because quite
196 Suck up to them, because they are the people who will make your job
197 easier. In particular, they'll be able to make your decisions for you,
200 So when you find somebody smarter than you are, just coast along. Your
[all …]
|
| /linux/Documentation/hwmon/ |
| H A D | submitting-patches.rst | 1 How to Get Your Patch Accepted Into the Hwmon Subsystem
6 increase the chances of your change being accepted.
18 * Please run your patch through 'checkpatch --strict'. There should be no
26 * If your patch generates checkpatch errors, warnings, or check messages,
32 * Please test your patch thoroughly. We are not your test group.
38 * If your patch (or the driver) is affected by configuration options such as
51 your patch into a cleanup part and the actual addition. This makes it easier
52 to review your changes, and to bisect any resulting problems.
60 * Running your patch or driver file(s) through checkpatch does not mean its
61 formatting is clean. If unsure about formatting in your new driver, run it
[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/driver-api/ |
| H A D | uio-howto.rst | 62 If you use UIO for your card's driver, here's what you get:
66 - develop the main part of your driver in user space, with all the
69 - bugs in your driver won't crash the kernel.
71 - updates of your driver can take place without recompiling the kernel.
82 :c:func:`mmap()` to access registers or RAM locations of your card.
112 To handle interrupts properly, your custom kernel module can provide its
130 - ``name``: The name of your device. It is recommended to use the name
131 of your kernel module for this.
133 - ``version``: A version string defined by your driver. This allows the
134 user space part of your driver to deal with different versions of the
[all …]
|
| /linux/arch/arm/mach-ep93xx/ |
| H A D | Kconfig | 32 Say 'Y' here if you want your kernel to support the
42 Say 'Y' here if you want your kernel to support the Cirrus
49 Say 'Y' here if you want your kernel to support the Cirrus
56 Say 'Y' here if you want your kernel to support the Cirrus
63 Say 'Y' here if you want your kernel to support the Cirrus
70 Say 'Y' here if you want your kernel to support the Cirrus
77 Say 'Y' here if you want your kernel to support the Cirrus
84 Say 'Y' here if you want your kernel to support the Cirrus
91 Say 'Y' here if you want your kernel to support the Cirrus
97 Say 'Y' here if you want your kernel to support the
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | spkguide.txt | 29 capabilities, depending on how your system administrator has installed
42 If your system administrator has installed Speakup to work with your
44 is to boot your system, and Speakup should come up talking. This
45 assumes of course that your synthesizer is a supported hardware
46 synthesizer, and that it is either installed in or connected to your
50 kernel with no default synthesizer. It is even possible that your
53 your synthesizer is supported but not available, complain to the person
54 who compiled and installed your kernel. Or better yet, go to the web
55 site, and learn how to patch Speakup into your own kernel source, and
56 build and install your own kernel.
[all …]
|
| H A D | README.rst | 57 your kernel.
63 directory where you have permissions (e.g. your home directory) and
82 Replace "x" for all versions bigger than the version "x" of your current
90 directly to the base 6.x kernel. For example, if your base kernel is 6.0
154 as expected. If you want to carry your existing configuration to a
171 your existing ./.config file and asking about
188 platforms of your architecture.
244 nonexistent controller card may confuse your other controllers.
266 ``make install`` if you have lilo installed or if your distribution has an
269 check your distribution's setup first.
[all …]
|
| /linux/Documentation/power/ |
| H A D | swsusp-dmcrypt.rst | 16 Now your system is properly set up, your disk is encrypted except for
19 an initrd that does your current crypto setup already.
21 At this point you want to encrypt your swap, too. Still you want to
32 within your running system. The easiest way to achieve this is
38 Now set up your kernel to use /dev/mapper/swap0 as the default
39 resume partition, so your kernel .config contains::
43 Prepare your boot loader to use the initrd you will create or
52 Finally you need to create or modify your initrd. Lets assume
57 named "swapkey". /etc/fstab of your initrd contains something
65 of your crypto devices, again by reading the setup from the
[all …]
|
| H A D | swsusp.rst | 12 ...kiss your data goodbye.
14 If you do resume from initrd after your filesystems are mounted...
20 problems. If your disk driver does not support suspend... (IDE does),
23 your hardware while system is suspended... well, it was not good idea;
47 - If you feel ACPI works pretty well on your system, you might try::
52 to RAM (provided your platform supports it), you can try::
57 support. For suspend and resume to work, make sure your disk drivers
138 You bought new UPS for your server. How do you install it without
142 You have your server on UPS. Power died, and UPS is indicating 30
250 but it may be unnecessarily slow. If you want your driver to stay simple,
[all …]
|
| /linux/Documentation/networking/ |
| H A D | nf_flowtable.rst | 17 flowtable through your ruleset. The flowtable infrastructure provides a rule
85 flowtable and add one rule to your forward chain::
111 You can identify offloaded flows through the [OFFLOAD] tag when listing your
129 You do not need to add the PPPoE and the VLAN devices to your flowtable,
130 instead the real device is sufficient for the flowtable to track your flows.
139 device (represented as eth0) in your switch/router.
159 your bridge port.
161 If you would like that your flowtable defines a fastpath between your bridge
162 ports and your IP forwarding path, you have to add your bridge ports (as
163 represented by the real netdevice) to your flowtable definition.
[all …]
|
| /linux/arch/openrisc/ |
| H A D | Kconfig | 93 Select this if your implementation features write through data caches.
110 Select this if your implementation has the Class II instruction l.ff1
116 Select this if your implementation has the Class II instruction l.fl1
122 Select this if your implementation has a hardware multiply instruction
128 Select this if your implementation has a hardware divide instruction
138 Select this if your implementation has support for the Class II
151 Select this if your implementation has support for the Class II
164 Select this if your implementation has support for the Class II
177 Select this if your implementation has support for the Class II
220 Say N here if you know that your OpenRISC processor has
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | 3270.rst | 22 VM-ESA operating system, define a 3270 to your virtual machine by using
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
32 another 3270 emulator, started from an xterm window on your PC or
34 and this Linux-390 3270 driver, you have another way of talking to your
50 you should rerun the configuration script every time your set of 3270s,
63 3270 console support, then the driver automatically converts your console
97 login prompts appear on your 3270s as soon as boot is complete (or
98 with emulated 3270s, as soon as you dial into your vm guest using the
104 3. Define graphic devices to your vm guest machine, if you
115 you have chosen 3270 console support, your console now behaves
[all …]
|
| /linux/lib/crc/ |
| H A D | Kconfig | 8 The CRC4 library functions. Select this if your module uses any of
14 The CRC7 library functions. Select this if your module uses any of
20 The CRC8 library functions. Select this if your module uses any of
26 The CRC16 library functions. Select this if your module uses any of
32 The CRC-CCITT library functions. Select this if your module uses any
38 The CRC-ITU-T library functions. Select this if your module uses
44 The CRC-T10DIF library functions. Select this if your module uses
60 The CRC32 library functions. Select this if your module uses any of
79 The CRC64 library functions. Select this if your module uses any of
|
| /linux/Documentation/scsi/ |
| H A D | libsas.rst | 35 After initializing your hardware, from the probe() function
36 you call sas_register_ha(). It will register your LLDD with
38 register your SAS driver with the sysfs SAS tree it creates.
39 It will then return. Then you enable your phys to actually
40 start OOB (at which point your driver will start calling the
49 Normally this is statically embedded to your driver's
58 And then all the phys are an array of my_phy in your HA
61 Then as you go along and initialize your phys you also
62 initialize the sas_phy struct, along with your own
89 address of the phy, possibly somewhere in your my_phy
[all …]
|
| /linux/drivers/input/mouse/ |
| H A D | Kconfig | 24 Say Y here if you have a PS/2 mouse connected to your system. This
48 your system.
58 your system.
68 your system.
78 your system.
100 your system.
110 TouchScreen connected to your system.
120 to your system.
129 to your system.
163 connected to your system.
[all …]
|
| /linux/arch/arm/mach-mvebu/ |
| H A D | Kconfig | 36 Say 'Y' here if you want your kernel to support boards based
52 Say 'Y' here if you want your kernel to support boards based
70 Say 'Y' here if you want your kernel to support boards based
85 Say 'Y' here if you want your kernel to support boards based
97 Say 'Y' here if you want your kernel to support boards based
112 Say 'Y' here if you want your kernel to support the
128 Say 'Y' here if you want your kernel to support boards based
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | sony-laptop.rst | 30 If your laptop model supports it, you will find sysfs files in the
67 by your particular laptop model.
115 your ACPI BIOS could have on your laptop), load the driver and
121 In your kernel logs you will find the list of all ACPI methods
122 the SNC device has on your laptop.
145 You can create other entries corresponding to your own laptop methods by
147 entry to this table with your get/set method names using the
150 Your mission, should you accept it, is to try finding out what
152 files and find out what is the impact on your laptop.
155 I will not disavow all knowledge of your actions :)
[all …]
|
| /linux/tools/usb/usbip/ |
| H A D | COPYING | 11 The licenses for most software are designed to take away your
13 License is intended to guarantee your freedom to share and change free
19 your programs, too.
28 To protect your rights, we need to make restrictions that forbid
39 We protect your rights with two steps: (1) copyright the software, and
88 you may at your option offer warranty protection in exchange for a fee.
90 2. You may modify your copy or copies of the Program or any portion
111 does not normally print such an announcement, your work based on
125 your rights to work written entirely by you; rather, the intent is to
143 years, to give any third party, for a charge no more than your
[all …]
|
| /linux/LICENSES/preferred/ |
| H A D | GPL-2.0 | 30 The licenses for most software are designed to take away your
32 License is intended to guarantee your freedom to share and change free
38 your programs, too.
47 To protect your rights, we need to make restrictions that forbid
58 We protect your rights with two steps: (1) copyright the software, and
107 you may at your option offer warranty protection in exchange for a fee.
109 2. You may modify your copy or copies of the Program or any portion
130 does not normally print such an announcement, your work based on
144 your rights to work written entirely by you; rather, the intent is to
162 years, to give any third party, for a charge no more than your
[all …]
|
| /linux/Documentation/arch/x86/i386/ |
| H A D | IO-APIC.rst | 20 usually worked around by the kernel. If your MP-compliant SMP board does
23 If your box boots fine with enabled IO-APIC IRQs, then your
43 In the unlikely case that your board does not create a working mp-table,
50 The actual numbers depend on your system, on your PCI cards and on their
86 so if you have your SCSI card (IRQ11) in Slot1, Tulip card (IRQ9) in
92 your PCI configuration::
96 note that this script won't work if you have skipped a few slots or if your
98 connected in some strange way). E.g. if in the above case you have your SCSI
|
| /linux/drivers/mtd/maps/ |
| H A D | Kconfig | 19 the physical address and size of the flash chips on your
32 physmap configuration options are done via your board's
43 are mapped on your particular target board. Refer to the
45 your board.
53 your particular board. If there is space, or aliases, in the
56 map which should hopefully be in the documentation for your
168 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
206 as an MTD device - with this you can reprogram your BIOS.
215 as an MTD device - with this you can reprogram your BIOS.
224 as an MTD device - with this you can reprogram your BIOS.
[all …]
|