Searched full:regard (Results 1 – 25 of 32) sorted by relevance
12
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 14 The key point to understand with regard to volatile is that its purpose is
89 to be a "stupid legacy" issue (Linus's words) in this regard; fixing it
|
| D | code-of-conduct.rst | 72 maintain confidentiality with regard to the reporter of an incident.
|
| D | 7.AdvancedTopics.rst | 139 authorship information; the git "am" tool does its best in this regard, but
145 pull. The git request-pull command can be helpful in this regard; it will
|
| D | 5.Posting.rst | 197 file "dontdiff" in the Documentation directory can help in this regard;
|
| /Documentation/virt/kvm/devices/ |
| D | mpic.rst | 55 regard to any subdivisions in chip documentation such as "internal"
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | toshiba,visconti-pinctrl.yaml | 33 pins it needs, and how they should be configured, with regard to muxer
|
| D | pinctrl-mt6797.txt | 27 pins it needs, and how they should be configured, with regard to muxer
|
| D | pinctrl-mt8192.yaml | 59 pins it needs, and how they should be configured, with regard to muxer
|
| D | pinctrl-mt65xx.txt | 48 pins it needs, and how they should be configured, with regard to muxer
|
| D | pinctrl-mt8183.txt | 30 pins it needs, and how they should be configured, with regard to muxer
|
| D | mediatek,mt6779-pinctrl.yaml | 82 pins it needs, and how they should be configured, with regard to muxer
|
| D | st,stm32-pinctrl.yaml | 121 pins it needs, and how they should be configured, with regard to muxer
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 62 regard to the annotated function's entry and exit.
|
| /Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 26 simulate the worst case scenario with regard to power failures. Consider the
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | omap-gpmc.txt | 89 - gpmc,wait-monitoring-ns: Start of wait monitoring with regard to valid
|
| /Documentation/core-api/ |
| D | packing.rst | 62 This corresponds to what most folks would regard to as "big endian", where
|
| /Documentation/driver-api/i3c/ |
| D | protocol.rst | 63 regard I3C is closer to a discoverable bus like USB than it is to I2C or SPI.
|
| /Documentation/filesystems/ |
| D | nilfs2.rst | 284 with regard to the design of NILFS2. It is allowed to replicate the
|
| /Documentation/driver-api/media/drivers/ |
| D | dvb-usb.rst | 47 TODO: dynamic enabling and disabling of the pid-filter in regard to number of
|
| /Documentation/hwmon/ |
| D | lm85.rst | 190 identifying the chip, the driver behaves no differently with regard to
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 50 *highly* architecture/toolchain specific. We cannot help you in this regard,
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 256 this regard.
508 the kernel's behavior in this regard has changed. As of 2.6.37 the
|
| /Documentation/crypto/ |
| D | descore-readme.rst | 216 perhaps some will still regard the result as a mess!
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memory.rst | 570 hierarchical_memory_limit # of bytes of memory limit with regard to hierarchy
572 hierarchical_memsw_limit # of bytes of memory+swap limit with regard to
|
| /Documentation/filesystems/caching/ |
| D | backend-api.rst | 88 This is left to the cache to handle; FS-Cache makes no effort in this regard.
|
12