Searched full:please (Results 1 – 25 of 886) sorted by relevance
12345678910>>...36
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 12 * It should be unnecessary to mention, but please read and follow:
18 * Please run your patch through 'checkpatch --strict'. There should be no
20 messages, please be prepared to explain.
22 * Please use the standard multi-line comment style. Do not mix C and C++
27 please refrain from explanations such as "I prefer that coding style".
32 * Please test your patch thoroughly. We are not your test group.
73 * Please list include files in alphabetic order.
75 * Please align continuation lines with '(' on the previous line.
95 and supported functions, please see Documentation/driver-api/driver-model/devres.rst.
131 * Your driver should be buildable as module. If not, please be prepared to
[all …]
|
| D | ltc4286.rst | 38 The driver is a client driver to the core PMBus driver. Please see
46 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
49 The shunt value in micro-ohms can be set via device tree at compile-time. Please
57 The driver supports standard PMBus driver platform data. Please see
|
| /Documentation/arch/nios2/ |
| D | nios2.rst | 8 system call ABI. Please see this link for more information on how compiling and booting
12 For reference, please see the following link:
23 Please refer to chapter "Application Binary Interface" in Nios II Processor Reference
|
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 9 The DVB mailing list linux-dvb is hosted at vger. Please see
14 reasons, please check the archive at https://linuxtv.org/pipermail/linux-dvb/.
18 of media boards. Please check it before asking newbie questions on the
|
| D | bt8xx.rst | 21 Please see Documentation/admin-guide/media/bttv-cardlist.rst for a complete
47 Please use the following options with care as deselection of drivers which
62 Then, on each of the above menu, please select your card-specific
108 For bug reports please send in a complete log with verbose=4 activated.
109 Please also see Documentation/admin-guide/media/ci.rst.
133 match the order where they're detected by the system. Please notice
141 In case of further problems please subscribe and send questions to
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,vf610-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
11 such as pull-up, speed, ode for this pin. Please refer to Vybrid VF610
40 Please refer to vf610-pinfunc.h in device tree source folder
|
| D | marvell,mvebu-pinctrl.txt | 7 Please refer to pinctrl-bindings.txt in this directory for details of the
17 Please refer to each marvell,<soc>-pinctrl.txt binding doc for supported SoCs.
23 common for all marvell,pins. Please refer to marvell,<soc>-pinctrl.txt for
|
| D | fsl,imx50-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
11 pull-up for this pin. Please refer to imx50 datasheet for the valid pad
|
| D | fsl,imx53-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
11 pull-up for this pin. Please refer to imx53 datasheet for the valid pad
|
| D | fsl,imx51-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
11 pull-up for this pin. Please refer to imx51 datasheet for the valid pad
|
| D | fsl,imx35-pinctrl.txt | 3 Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
11 pull-up for this pin. Please refer to imx35 datasheet for the valid pad
|
| /Documentation/usb/ |
| D | usb-serial.rst | 53 For any questions or problems with this driver, please contact
98 For any questions or problems with this driver, please contact Greg
109 For others, please use module parameters to specify the product and vendor
119 the USB connection. Please visit http://synce.sourceforge.net which
150 For any questions or problems with the driver, please contact Ganesh
182 For any questions or problems with this driver, please contact Brian
207 For any questions or problems with this driver, please contact Hugh
221 For any questions or problems with this driver, please contact Bill Ryder.
227 This is an ISDN TA. Please report both successes and troubles to
275 The hid->com adapter can run at a maximum baud of 115200bps. Please note
[all …]
|
| /Documentation/rust/ |
| D | index.rst | 7 in the kernel, please read the quick-start.rst guide.
22 If you are an end user, please note that there are currently no in-tree
47 Please see the :ref:`Code documentation <rust_code_documentation>` section for
|
| /Documentation/process/ |
| D | maintainer-tip.rst | 25 overall x86 maintainers. Please Cc the overall x86 maintainers on
31 team. Please always Cc the Linux Kernel mailing list (LKML)
120 'genirq/core:'. Please do not use file names or complete file paths as
247 subject line, please use the format 'function_name()'. Omitting the
293 Please say instead::
369 If the patch should be backported to stable, then please add a '``Cc:
375 For referring to an email posted to the kernel mailing lists, please
393 patch when applying it to your git tree. In that case, please use the
401 Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
413 Therefore, for 'volatile' documents, please create an entry in the kernel
[all …]
|
| D | cve.rst | 24 assigned CVEs, please `subscribe
45 should have a CVE assigned to it, please email them at <cve@kernel.org>
49 feel you have found an unfixed security issue, please follow the
57 have a CVE assigned before an issue is resolved with a commit, please
91 CVE team should not be treated as a valid CVE. Please notify the
101 determine, it is not up to the CVE assignment team. Please do not
|
| D | security-bugs.rst | 8 disclosed as quickly as possible. Please report security bugs to the
17 If you already have a fix, please include it with your report, as
23 will be to diagnose and fix. Please review the procedure outlined in
29 Please send plain text emails without attachments where possible.
77 Please note that the respective policies and rules are different since
|
| /Documentation/devicetree/bindings/thermal/ |
| D | max77620_thermal.txt | 11 #thermal-sensor-cells: For more details, please refer to
15 For more details, please refer generic thermal DT binding document
18 Please refer <devicetree/bindings/mfd/max77620.txt> for mfd DT binding
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs4341.txt | 11 For required properties on I2C-bus, please consult
13 For required properties on SPI-bus, please consult
|
| D | atmel_ac97c.txt | 7 - ac97-gpios: Please refer to soc-ac97link.txt, only ac97-reset is used
9 - pinctrl-names, pinctrl-0: Please refer to pinctrl-bindings.txt
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-multicolor | 11 For additional details please refer to
23 For additional details please refer to
|
| D | sysfs-devices | 11 Please do not rely on the format of this tree because of
13 the tree, please use the /sys/class structure and rely
|
| /Documentation/devicetree/bindings/mfd/ |
| D | lp3943.txt | 9 For the LP3943 GPIO properties please refer to:
12 For the LP3943 PWM properties please refer to:
|
| /Documentation/sound/soc/ |
| D | platform.rst | 48 Please refer to the ALSA driver documentation for details of audio DMA.
65 Please see codec.rst for a description of items 1 - 4.
78 Please see DPCM.txt for a description of item 4.
|
| /Documentation/devicetree/bindings/media/ |
| D | atmel-isi.txt | 9 property; please refer to clock-bindings.txt.
11 - pinctrl-names, pinctrl-0: please refer to pinctrl-bindings.txt.
14 'port' child node with child 'endpoint' node. Please refer to the bindings
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 6 please contact maintainer of this file or JF project.
8 Please also note that purpose of this file is easier to read for non
10 comment or update of this file, please try to update Original(English)
|
12345678910>>...36