| /linux-6.12.1/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 66 Your distro should already have GnuPG installed by default, you just
93 edit your ``~/.gnupg/gpg-agent.conf`` file to set your own values::
102 beginning of your shell session. You may want to check your rc files
108 Protect your PGP key
116 You should also make a new key if your current one is weaker than 2048
143 private key on your chain.
150 3. A single subkey may have multiple capabilities (e.g. your **[C]** key
151 can also be your **[S]** key).
167 If you used the default parameters when generating your key, then that
176 The long line under the ``sec`` entry is your key fingerprint --
[all …]
|
| 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 …]
|
| 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 …]
|
| 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.
19 This documentation assumes that you're using ``git`` to prepare your patches.
21 use it, it will make your life as a kernel developer and in general much
45 Describe your changes
48 Describe your problem. Whether your patch is a one-line bug fix or
60 from upstream, so include anything that could help route your change
69 different workloads. Describe the expected downsides of your
77 The maintainer will thank you if you write your patch description in a
81 Solve only one problem per patch. If your description starts to get
[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
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 …]
|
| 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 …]
|
| /linux-6.12.1/arch/arm/mach-orion5x/ |
| 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-6.12.1/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.
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-6.12.1/Documentation/admin-guide/ |
| D | quickly-build-trimmed-linux.rst | 20 If your system uses techniques like Secure Boot, prepare it to permit starting
22 building Linux; make sure to have 12 Gigabyte free space in your home directory.
24 you then use to configure, build and install your own kernel::
30 # Hint: it's recommended to tag your build at this point. See below for details.
57 Compiling your own Linux kernel is easy in principle. There are various ways to
93 ensure the system will permit your self-compiled kernel to boot later. The
115 sources and build artifacts 12 Gigabyte in your home directory should
117 section for the step that explains adjusting your kernels build
161 If you deepened your clone, you instead of ``origin/master`` can specify the
186 * If you patched your kernel or have one of the same version installed already,
[all …]
|
| 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 …]
|
| D | verify-bugs-and-bisect-regressions.rst | 36 aspects, all of which might be essential in your present case.]*
51 * **Preparations**: set up everything to build your own kernels::
58 # * Ensure to have 15 Gigabyte free space in your home directory.
104 # * Check how much space your self-built kernel actually needs, which
139 a) Retrieve the sources for your 'bad' version::
166 d) Once your finished the bisection, put a few things away::
225 This guide describes how to set up your own Linux kernels for investigating bugs
227 depends on your issue:
229 Execute all steps till the end of *segment 1* to **verify if your kernel problem
232 as then your want to at least continue with *segment 2* to **check if the issue
[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
248 b. Limit your CPU frequency so that a CPU-frequency
252 be able to build your kernel with CONFIG_CPU_FREQ=n to
[all …]
|
| D | reporting-issues.rst | 21 In all other cases try your best guess which kernel part might be causing the
41 separately. While writing your report, include all information relevant to the
43 regressions mailing list (regressions@lists.linux.dev) to your report. Also try
63 a slightly different order. That's in your interest, to make sure you notice
70 document and reporting the issue to your vendor instead, unless you are
74 * Perform a rough search for existing reports with your favorite internet
88 * Ensure your system does not enhance its kernels by building additional
90 without your knowledge.
92 * Check if your kernel was 'tainted' when the issue occurred, as the event
111 thoroughly for reports that might match your issue. If you find anything,
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/arch/arm/mach-ep93xx/ |
| 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-6.12.1/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 …]
|
| /linux-6.12.1/fs/reiserfs/ |
| D | README | 11 other licenses. If you add your code to governed files, and don't
12 want it to be owned by Hans Reiser, put your copyright label on that
15 Reiser, and by adding your code to it, widely distributing it to
19 to license code labeled as owned by you on your behalf other than
25 right to decline to allow him to license your code contribution other
52 mkreiserfs and other utilities are in reiserfs/utils, or wherever your
63 Yes, if you update your reiserfs kernel module you do have to
64 recompile your kernel, most of the time. The errors you get will be
65 quite cryptic if your forget to do so.
70 Hideous Commercial Pitch: Spread your development costs across other OS
[all …]
|
| /linux-6.12.1/arch/openrisc/ |
| D | Kconfig | 85 Select this if your implementation features write through data caches.
102 Select this if your implementation has the Class II instruction l.ff1
108 Select this if your implementation has the Class II instruction l.fl1
114 Select this if your implementation has a hardware multiply instruction
120 Select this if your implementation has a hardware divide instruction
130 Select this if your implementation has support for the Class II
143 Select this if your implementation has support for the Class II
156 Select this if your implementation has support for the Class II
169 Select this if your implementation has support for the Class II
212 Say N here if you know that your OpenRISC processor has
[all …]
|
| /linux-6.12.1/Documentation/networking/ |
| 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-6.12.1/Documentation/arch/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 …]
|
| /linux-6.12.1/Documentation/scsi/ |
| 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-6.12.1/Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 10 It's a one-way downstream-only cable modem, meaning that your upstream net link
11 is provided by your regular phone modem.
26 2. Several PPP scripts which live in /etc/ppp to make connecting via your
41 3. The standard isapnp tools. These are necessary to configure your SB1000
44 If you don't have these installed as a standard part of your Linux
49 or check your Linux distribution binary CD or their web site. For help with
60 you prefer, in the top kernel tree directory to set up your kernel
67 by isapnp to access your PnP cards. This is the value of READPORT in
72 4. Boot your new kernel following the usual procedures.
76 IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
[all …]
|
| /linux-6.12.1/drivers/input/mouse/ |
| 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-6.12.1/drivers/input/touchscreen/ |
| D | Kconfig | 34 and your board-specific setup code includes that in its
38 on your board, you will also get hwmon interfaces for the voltage
51 AD7877 controller, and your board-specific initialization
111 controller chip in your system.
124 such as AT42QT602240/ATMXT224, connected to your system.
158 your system.
170 connected to your system.
231 to your system. You will also need to select appropriate
303 your system.
315 your system.
[all …]
|
| /linux-6.12.1/arch/arm/mach-mvebu/ |
| 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
|