Searched refs:arrange (Results 1 – 21 of 21) sorted by relevance
| /Linux-v5.4/Documentation/driver-api/ |
| D | dell_rbu.rst | 79 image file and then arrange all these packets back to back in to one single
|
| /Linux-v5.4/Documentation/security/ |
| D | siphash.rst | 87 is to simply arrange the members of the struct in descending order of size,
|
| /Linux-v5.4/drivers/media/pci/intel/ipu3/ |
| D | ipu3-cio2.c | 1909 static void arrange(void *ptr, size_t elem_size, size_t elems, size_t start) in arrange() function
1968 arrange(q->fbpt, sizeof(struct cio2_fbpt_entry) * CIO2_MAX_LOPS, in cio2_fbpt_rearrange()
1970 arrange(q->bufs, sizeof(struct cio2_buffer *), in cio2_fbpt_rearrange()
|
| /Linux-v5.4/Documentation/spi/ |
| D | spidev.rst | 32 The simplest way to arrange to use this driver is to just list it in the
|
| D | spi-summary.rst | 596 This must not sleep. Its responsibility is to arrange that the
|
| /Linux-v5.4/drivers/mtd/chips/ |
| D | Kconfig | 49 This option defines the way in which the CPU attempts to arrange
|
| /Linux-v5.4/Documentation/networking/ |
| D | sfp-phylink.rst | 239 and arrange to destroy the phylink in the probe failure path as
|
| D | snmp_counter.rst | 728 to re-arrange data in these skb. E.g. if a SACK block acknowledges seq
|
| /Linux-v5.4/Documentation/vm/ |
| D | numa.rst | 42 application software must arrange for a large majority of the memory references
|
| /Linux-v5.4/Documentation/crypto/ |
| D | userspace-if.rst | 274 The user space caller must arrange the aforementioned information in the
|
| /Linux-v5.4/drivers/usb/gadget/legacy/ |
| D | Kconfig | 38 this device, and arrange to select an appropriate configuration.
|
| /Linux-v5.4/Documentation/admin-guide/blockdev/ |
| D | paride.rst | 384 your paride drivers as modules, and arrange to do the printer reset
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.megaraid | 418 re-arrange the code to eliminate the need for most (all) of the
|
| D | scsi_mid_low_api.txt | 289 arrange for the SCSI mid level to be loaded and initialized before any LLD
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | porting.rst | 677 data structures needs exclusion for some reason, arrange it
|
| D | xfs-delayed-logging-design.txt | 531 very difficult and complex to arrange. It is possible to do, but there is a
|
| D | vfs.rst | 518 if it needs to be otherwise pinned, arrange for its release by
|
| /Linux-v5.4/Documentation/driver-api/gpio/ |
| D | legacy.rst | 292 pullup/pulldown. Platform software should arrange that any such details are
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | power-management.rst | 720 switch that gates connections. Userspace must arrange
|
| /Linux-v5.4/tools/memory-model/Documentation/ |
| D | explanation.txt | 742 arrange for the store to be co-later than (i.e., to overwrite) any
|
| /Linux-v5.4/Documentation/ |
| D | memory-barriers.txt | 141 appears to be maintained. Similarly, the compiler may also arrange the
|
