| /Documentation/process/ |
| 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
56 making. Do not let their form of expression or your own pride keep that
63 reviewers. If you believe that the reviewer has misunderstood your code,
65 suggested change, describe it and justify your solution to the problem. If
66 your explanations make sense, the reviewer will accept them. Should your
69 be easy to become blinded by your own solution to a problem to the point
[all …]
|
| D | maintainer-pgp-guide.rst | 66 Your distro should already have GnuPG installed by default, you just
92 You can put that in your ``.bashrc`` to make sure it's always the case.
111 edit your ``~/.gnupg/gpg-agent.conf`` file to set your own values::
120 beginning of your shell session. You may want to check your rc files
127 You will need to regularly refresh your keyring in order to get the
133 Check the full path to your ``gpg`` or ``gpg2`` command and use the
138 Protect your master PGP key
146 You should also make a new key if your current one is weaker than 2048 bits
169 lose your private subkey, it cannot be recreated from the master key
186 If you used the default parameters when generating your key, then that
[all …]
|
| D | submitting-patches.rst | 3 Submitting patches: the essential guide to getting your code into the kernel
9 can greatly increase the chances of your change being accepted.
22 control system; if you use ``git`` to prepare your patches, you'll find much
25 your life as a kernel developer easier.
48 If you must generate your patches by hand, use ``diff -up`` or ``diff -uprN``
53 generated by :manpage:`diff(1)`. When creating your patch, make sure to
68 vi $MYFILE # make your change
73 or unmodified kernel source tree, and generate a ``diff`` against your
87 Make sure your patch does not include any extra files which do not
88 belong in a patch submission. Make sure to review your patch -after-
[all …]
|
| 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 …]
|
| 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
215 will learn the basics of getting your patch into the Linux kernel tree,
360 One of the best ways to put into practice your hacking skills is by fixing
363 your skills, and other developers will be aware of your presence. Fixing
405 If multiple people respond to your mail, the CC: list of recipients may
411 Remember to keep the context and the attribution of your replies intact,
412 keep the "John Kernelhacker wrote ...:" lines at the top of your reply, and
413 add your statements between the individual quoted sections instead of
416 If you add patches to your mail, make sure they are plain readable text
[all …]
|
| D | email-clients.rst | 13 If you are new to ``git`` then send your first patch to yourself. Save it
35 Don't let your email client do automatic word wrapping for you.
36 This can also corrupt your patch.
40 If you configure your email client to send emails with UTF-8 encoding,
127 way around this is to compose your email with word wrap enabled, then save
128 it as a draft. Once you pull it up again from your drafts it is now hard
132 At the bottom of your email, put the commonly-used patch delimiter before
133 inserting your patch: three hyphens (``---``).
136 :menuselection:`insert file` and choose your patch.
143 disabled in the Options menu isn't enough. Thus, if your patch has very
[all …]
|
| 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 …]
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 1 How to Get Your Patch Accepted Into the Hwmon Subsystem
6 increase the chances of your change being accepted.
19 * Please run your patch through 'checkpatch --strict'. There should be no
27 * If your patch generates checkpatch errors, warnings, or check messages,
33 * Please test your patch thoroughly. We are not your test group.
39 * If your patch (or the driver) is affected by configuration options such as
52 your patch into a cleanup part and the actual addition. This makes it easier
53 to review your changes, and to bisect any resulting problems.
61 * Running your patch or driver file(s) through checkpatch does not mean its
62 formatting is clean. If unsure about formatting in your new driver, run it
[all …]
|
| /Documentation/ioctl/ |
| 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 …]
|
| /Documentation/power/ |
| 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 …]
|
| /Documentation/driver-api/ |
| 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 …]
|
| /Documentation/admin-guide/ |
| D | reporting-bugs.rst | 18 contact your Linux distribution or embedded vendor for support.
31 Identifying which part of the Linux kernel might be causing your issue
32 increases your chances of getting your bug fixed. Simply posting to the
33 generic linux-kernel mailing list (LKML) may cause your bug report to be
38 maintainer doesn't answer, then expand your scope to mailing lists like
50 To find out where to send an emailed bug report, find your subsystem or
52 entries, and send your bug report to the person(s) listed in the "M:"
96 a netconsole trace, or type the message from your screen into the bug
97 report. Please read "Documentation/admin-guide/bug-hunting.rst" before posting your
105 relevant to your bug, feel free to exclude it.
[all …]
|
| D | kernel-per-CPU-kthreads.rst | 113 3. Once your application has started, prevent CPU-hotplug operations
116 bring it back online before you start your application.)
125 3. Once your application has started, prevent CPU-hotplug operations
128 bring it back online before you start your application.)
137 3. Once your application has started, prevent CPU-hotplug operations
140 bring it back online before you start your application.)
230 1. Run your workload at a real-time priority, which will allow
243 3. Do any of the following needed to avoid jitter that your
246 a. Build your kernel with CONFIG_SLUB=y rather than
252 c. Limit your CPU frequency so that a CPU-frequency
[all …]
|
| 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 5.x kernel. For example, if your base kernel is 5.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.
236 nonexistent controller card may confuse your other controllers.
261 kernel makefiles, but you may want to check your particular lilo setup first.
286 are installing a new kernel with the same version number as your
[all …]
|
| /Documentation/s390/ |
| 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 …]
|
| /Documentation/scsi/ |
| D | libsas.txt | 32 After initializing your hardware, from the probe() function
33 you call sas_register_ha(). It will register your LLDD with
35 register your SAS driver with the sysfs SAS tree it creates.
36 It will then return. Then you enable your phys to actually
37 start OOB (at which point your driver will start calling the
43 Normally this is statically embedded to your driver's
50 And then all the phys are an array of my_phy in your HA
53 Then as you go along and initialize your phys you also
54 initialize the sas_phy struct, along with your own
73 address of the phy, possibly somewhere in your my_phy
[all …]
|
| D | NinjaSCSI.txt | 18 [1] Check your PC card is true "NinjaSCSI-3" card.
19 If you installed pcmcia-cs already, pcmcia reports your card as UNKNOWN
21 your console or log file.
39 kernel source, I recommend rebuilding your kernel; this eliminates
108 If you eject card when doing some operation for your SCSI device or suspend
109 your computer, you encount some *BAD* error like disk crash.
111 your data. Please backup your data when you use this driver.
122 your SCSI device name(hard drive, CD-ROM, etc...)
|
| /Documentation/networking/ |
| D | driver.txt | 7 there is no way your device can tell ahead of time when it's
41 And then at the end of your TX reclamation event handling:
65 3) Do not forget that once you return NETDEV_TX_OK from your
66 ndo_start_xmit method, it is your driver's responsibility to free
69 For example, this means that it is not allowed for your TX
81 1) Any hardware layer address you obtain for your device should
|
| D | ipddp.txt | 13 Through this driver you can either allow your Linux box to communicate
15 for your AppleTalk users.
26 AppleTalk-IP decapsulation needs to be compiled into your kernel. You
44 which enables you to add routes to the kernel for your Macs by hand.
46 proper IP Gateway and IP addresses for your machine. Included in this
54 You will also need to add the proper routes to route your Linux box's IP
|
| /Documentation/x86/i386/ |
| 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
|
| /Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 20 interface is likely not to work. This document may then not cover your situation
38 Shut the computer down to protect your GPU.
42 on your chipset.
73 Speed in RPM of your fan.
75 Your fan can be driven in different modes:
87 depending on your hardware.
|
| /Documentation/networking/device_drivers/ |
| D | sb1000.txt | 4 It's a one-way downstream-only cable modem, meaning that your upstream net link
5 is provided by your regular phone modem.
20 2.) Several PPP scripts which live in /etc/ppp to make connecting via your
35 3.) The standard isapnp tools. These are necessary to configure your SB1000
38 If you don't have these installed as a standard part of your Linux
43 or check your Linux distribution binary CD or their web site. For help with
53 you prefer, in the top kernel tree directory to set up your kernel
60 by isapnp to access your PnP cards. This is the value of READPORT in
65 4.) Boot your new kernel following the usual procedures.
69 IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
[all …]
|
| /Documentation/admin-guide/laptops/ |
| 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 …]
|
| /Documentation/usb/ |
| D | iuu_phoenix.rst | 8 This module provide a serial interface to use your
11 used by your favorite application to pilot the IUU
14 occur and your system may freeze. As far I now,
16 guru, so don't blame me if your system is unstable
70 - xmas is completely useless except for your eyes. This is one of my friend who was
87 work for your software, disable detection mechanism in it.
|
| /Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 29 Step 4 will create a new dummy policy valid for your
31 It will compile the policy, will set your ``SELINUXTYPE`` to
33 as ``dummy``, and relabel your filesystem.
|