Home
last modified time | relevance | path

Searched full:shouldn (Results 1 – 25 of 75) sorted by relevance

123

/Documentation/admin-guide/namespaces/
Dcompatibility-list.rst27 In both cases, tasks shouldn't try exposing this ID to some
35 words, user 10 in one user namespace shouldn't have the same
/Documentation/vm/
Dpage_migration.rst182 shouldn't expect to preserve values in those fields.
199 Driver shouldn't touch the page.lru field while in the migratepage() function.
226 so driver shouldn't access page->mapping directly. Instead, driver should
256 VM so it shouldn't touch the page.lru field.
258 shouldn't use PG_isolated for its own purposes.
/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst16 The devices' relationships (when using a webcam, end-users shouldn't
/Documentation/devicetree/bindings/crypto/
Dinside-secure-safexcel.txt19 Two compatibles are kept for backward compatibility, but shouldn't be used for
/Documentation/devicetree/bindings/
DABI.rst29 3) Bindings can be augmented, but the driver shouldn't break when given
/Documentation/core-api/irq/
Dirqflags-tracing.rst51 shouldn't be)
/Documentation/powerpc/
Dcpu_features.rst37 that shouldn't be used by writing nop's over it. Using cpufeatures requires
/Documentation/userspace-api/media/
Dcec.h.rst.exceptions20 # Shouldn't them be documented?
29 # Part of CEC 2.0 spec - shouldn't be documented too?
/Documentation/devicetree/bindings/arm/
Dpmu.yaml70 the interrupt-affinity property shouldn't be present).
/Documentation/security/
Dsak.rst15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
/Documentation/usb/
Draw-gadget.rst8 currently a strictly debugging feature and shouldn't be used in
/Documentation/devicetree/bindings/phy/
Dphy-mtk-xsphy.txt20 shouldn't use the property.
/Documentation/devicetree/bindings/pci/
Dpci-keystone.txt66 phy-names shouldn't be present.
/Documentation/admin-guide/device-mapper/
Dera.rst38 Possibly move to a new era. You shouldn't assume the era has
/Documentation/admin-guide/cgroup-v1/
Dmemcg_test.rst290 In this case, panic_on_oom shouldn't be invoked and tasks
291 in other groups shouldn't be killed.
/Documentation/devicetree/bindings/net/
Dmarvell-pp2.txt50 for backward compatibility but shouldn't be used for new
/Documentation/filesystems/
Dbefs.rst63 figure it out yourself (it shouldn't be hard), or mail the maintainer
/Documentation/networking/device_drivers/ethernet/3com/
D3c509.rst22 card's 3Com model number, 3c509. They are all 10mb/s ISA-bus cards and shouldn't
46 IRQ, and transceiver settings, although this capability shouldn't generally be
/Documentation/core-api/
Ddma-attributes.rst120 where allocation failures are not a problem, and shouldn't bother the logs.
/Documentation/driver-api/
Dinterconnect.rst100 software shouldn't rely on format details change between kernel versions.
/Documentation/block/
Dbiovecs.rst126 shouldn't use them because the bio may have been split before it reached the
/Documentation/devicetree/bindings/regulator/
Dregulator.yaml44 at boot but shouldn't prevent it from being turned off later.
/Documentation/admin-guide/laptops/
Dsonypi.rst70 with it and it shouldn't be required anyway if
/Documentation/userspace-api/media/v4l/
Dlibv4l-introduction.rst77 Since those functions are emulations of the old V4L1 API, it shouldn't
/Documentation/process/
Dsubmitting-drivers.rst97 shouldn't use inline x86 assembler in your driver without

123