Searched full:mention (Results 1 – 25 of 93) sorted by relevance
1234
/linux-6.8/Documentation/admin-guide/ |
D | reporting-issues.rst | 145 issue. Always mention a few things: the latest kernel version you installed 196 issue and ideally explain how to reproduce it. Mention the first version 260 so, you might want to mention you'd like to see the issue fixed in the 684 'Mail:' instead. Those mention the name and the email addresses for the 1006 Note, if you can't get this to work, simply skip this step and mention the 1072 issue. Always mention a few things: the latest kernel version you installed 1089 That's why this text will only mention a few of the essentials as well as 1100 Things each report should mention 1121 * if you are dealing with a regression and performed a bisection, mention the 1150 * Put the files aside and mention you will send them later in individual [all …]
|
/linux-6.8/Documentation/arch/powerpc/ |
D | mpc52xx.rst | 42 mention you/your company in the copyright of some code, I'll correct it
|
/linux-6.8/Documentation/devicetree/bindings/gpio/ |
D | spear_spics.txt | 25 * #gpio-cells: should be 1 and will mention chip select number
|
/linux-6.8/Documentation/devicetree/bindings/sound/ |
D | nvidia,tegra210-i2s.yaml | 47 as source, can mention this clock as parent in the DT bindings.
|
/linux-6.8/Documentation/usb/ |
D | functionfs.rst | 35 What I also want to mention is that the FunctionFS is designed in such
|
/linux-6.8/Documentation/admin-guide/cifs/ |
D | authors.rst | 65 mention to the Stanford Checker (SWAT) which pointed out many minor
|
/linux-6.8/Documentation/virt/kvm/x86/ |
D | running-nested-guests.rst | 220 - Mention that you are in a "nested" setup. If you are running any kind 223 *mention* that they're using nested virtualization.
|
/linux-6.8/Documentation/driver-api/memory-devices/ |
D | ti-gpmc.rst | 42 Then there may be cases where peripheral datasheet doesn't mention
|
/linux-6.8/scripts/ |
D | generate_rust_analyzer.py | 118 # We explicitly mention the top-level folders we want to cover.
|
D | documentation-file-ref-check | 12 # to mention a past documentation file, for example, to give credits for
|
/linux-6.8/drivers/rtc/ |
D | rtc-max6902.c | 105 * does not mention a delay being required anywhere... */ in max6902_set_time()
|
/linux-6.8/scripts/basic/ |
D | fixdep.c | 53 * internet connection right now, so I rather don't mention names 84 * we cannot miss a rebuild. Since people tend to not mention totally
|
/linux-6.8/drivers/hwmon/pmbus/ |
D | max15301.c | 7 * Even though the specification does not specifically mention it,
|
/linux-6.8/Documentation/livepatch/ |
D | system-state.rst | 38 Each livepatch defines an array of struct klp_states. They mention
|
/linux-6.8/drivers/gpu/drm/amd/amdkfd/ |
D | kfd_mqd_manager.h | 62 * Another important thing to mention is that each queue has a MQD that keeps
|
/linux-6.8/drivers/soundwire/ |
D | bus.h | 94 * SoundWire spec has no mention of ports for Master interface but the
|
/linux-6.8/net/ax25/ |
D | ax25_ds_subr.c | 41 * DAMA spec mention the following behaviour as seen in ax25_ds_enquiry_response()
|
/linux-6.8/Documentation/hwmon/ |
D | submitting-patches.rst | 12 * It should be unnecessary to mention, but please read and follow:
|
/linux-6.8/Documentation/maintainer/ |
D | pull-requests.rst | 66 diffstat anyway, and if you didn't mention it, I'll just be extra
|
D | rebasing-and-merging.rst | 179 how you would resolve things. Mention that branch in your pull request,
|
/linux-6.8/arch/arm64/include/asm/ |
D | percpu.h | 144 * Not to mention it'll break the actual preemption model for missing a
|
/linux-6.8/Documentation/arch/arm/nwfpe/ |
D | netwinder-fpe.rst | 44 mention of this is made in the ARM manuals.
|
/linux-6.8/Documentation/admin-guide/blockdev/ |
D | floppy.rst | 241 sure to mention also the type of the filesystem in the subject line.
|
/linux-6.8/tools/usb/usbip/ |
D | INSTALL | 133 `README' should mention any `--enable-' and `--with-' options that the
|
/linux-6.8/tools/perf/Documentation/ |
D | security.txt | 114 9. Login and check that dmesg output doesn't mention that perf_event class is unknown to SELinux su…
|
1234