Searched full:consider (Results 1 – 25 of 231) sorted by relevance
12345678910
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 36 Consider the video playback case in which a video is played in a specific
76 When reporting a bug related to DC, consider attaching this log before and
115 So, when reporting bugs related to features such as PSR and ABM, consider
|
| D | dc-glossary.rst | 8 consider asking in the amdgfx and update this page.
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 142 performance counter sampling instructions) consider exposing those also.
159 * Consider ditching any synchronous wait ioctls with timeouts and just deliver
177 lifetime of a file descriptor. Consider using a 1:1 mapping if your resource
197 of objects, but consider using inode numbers on your shared file descriptors
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
| D | handling-regressions.rst | 77 to the list. Consider checking the list archives beforehand, if the reporter
81 When doing either, consider making the Linux kernel regression tracking bot
168 * Do not consider regressions from the current cycle as something that can wait
197 * Always consider reverting the culprit, as it's often the quickest and least
207 * Consider CCing Linus on discussions or patch review, if a regression seems
212 * For urgent regressions, consider asking Linus to pick up the fix straight
219 CC; in it, summarize the situation while asking him to consider picking up
262 the particular fix. Also consider sending git pull requests more often than
275 search in Linux distributions and Git forges. Also consider asking other
408 regzbot consider your mail as a regressions report added to the tracking, as
[all …]
|
| /Documentation/staging/ |
| D | speculation.rst | 21 checks to be ignored by code which is speculatively executed. Consider the
48 result in sensitive information being leaked. Consider the following
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 18 does not parse / consider data which is already covered by the boot
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-frequency-adf4350 | 20 is updated. Consider to use out_altvoltageY_powerdown to power
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.yaml | 16 there are no competing masters to consider for gates and therefore there is
|
| /Documentation/leds/ |
| D | uleds.rst | 23 any valid sysfs device node name, but consider using the LED class naming
|
| /Documentation/admin-guide/mm/ |
| D | index.rst | 19 familiar with it, consider reading Documentation/admin-guide/mm/concepts.rst.
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 14 There are a few reasons why you might want to consider building your firmware
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 25 defined in the DT Spec. If there isn't one, consider adding it.
47 - DO use a vendor prefix on device-specific property names. Consider if
|
| /Documentation/firmware-guide/acpi/ |
| D | i2c-muxes.rst | 10 Consider this topology::
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-common.yaml | 114 Vendor-specific clock names. Consider using the generic names
171 Vendor-specific reset names. Consider using the generic names
198 Vendor-specific PHY names. Consider using the generic
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 59 Consider an hypothetical dual-core asymmetric CPU capacity system where
94 OPPs. Consider the same CPUs as above (i.e. same work_per_hz()) with:
153 directly impacted by the current OPP the CPU is running at. Consider running a
163 Now, consider running the *same* workload at frequency F/2::
188 Consider the system described in 1.3.2., i.e.::
377 sleeps, if at all - it thus rarely wakes up, if at all. Consider::
|
| /Documentation/arch/arm/sunxi/ |
| D | clocks.rst | 13 steps, one can gate it and keep the system running. Consider this
|
| /Documentation/devicetree/bindings/mfd/ |
| D | mfd.txt | 21 should consider all subnodes of the MFD device as separate and independent
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 72 There is one more thing to consider - splicing. It's not an operation
163 Suppose deadlocks are possible. Consider the minimal deadlocked
213 Consider the order in which directories are locked by the
270 Now consider the loop created by the operation. It passes through either
|
| /Documentation/doc-guide/ |
| D | contributing.rst | 171 have fixed a few, please consider moving on to more advanced tasks, leaving
185 As with any patch to any project, please consider whether your change is
196 Whenever you are working with a document, please consider whether it is
224 this information with caution, and please consider sending patches
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 9 # understand why this recursive dependency issue occurs lets consider what
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | charger-manager.yaml | 72 description: state of charge to consider as full battery in %
76 description: capcity to consider as full battery in uAh
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 19 so crossbar bar driver should not consider them as free
|
| /Documentation/tools/rv/ |
| D | Makefile | 26 $(info ** Consider installing the latest rst2man from your)
|
| /Documentation/tools/rtla/ |
| D | Makefile | 27 $(info ** Consider installing the latest rst2man from your)
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 31 be wise to consider alternatives such as recompilation, emulation or
97 Calls to ``sched_setaffinity(2)`` for a 32-bit task will consider only
|
12345678910