Home
last modified time | relevance | path

Searched refs:NEVER (Results 1 – 12 of 12) sorted by relevance

/linux-5.19.10/Documentation/usb/
Dlinux.inf40 ; NEVER REMOVE THE FOLLOWING REFERENCE FOR NETRNDIS.INF
/linux-5.19.10/include/linux/sunrpc/
Dcache.h225 #define NEVER (0x7FFFFFFF) macro
/linux-5.19.10/Documentation/devicetree/bindings/clock/
Dsilabs,si5351.txt57 3 = clock output is NEVER disabled
/linux-5.19.10/Documentation/trace/
Dhwlat_detector.rst31 Note that the hwlat detector should *NEVER* be used in a production environment.
/linux-5.19.10/Documentation/timers/
Dtimekeeping.rst32 It will ideally NEVER stop ticking as long as the system is running. It
/linux-5.19.10/Documentation/driver-api/usb/
DURB.rst231 NEVER SLEEP IN A COMPLETION HANDLER.
/linux-5.19.10/net/
DKconfig46 Newly written code should NEVER need this option but do
/linux-5.19.10/drivers/char/
DKconfig339 should NEVER idly tamper with it. See Ralf Brown's interrupt list
/linux-5.19.10/Documentation/process/
Dcoding-style.rst436 Maybe there are other cases too, but the rule should basically be to NEVER
601 Comments are good, but there is also a danger of over-commenting. NEVER
/linux-5.19.10/Documentation/filesystems/
Dconfigfs.rst381 appear in a filesystem. A subsystem is NEVER to touch the filesystem
/linux-5.19.10/drivers/gpu/drm/msm/adreno/
Da2xx.xml.h171 NEVER = 0, enumerator
/linux-5.19.10/Documentation/driver-api/
Dipmi.rst333 that you should NEVER mess with the "done" field of a message, that is