Searched refs:attachments (Results 1 – 9 of 9) sorted by relevance
| /linux-4.1.27/Documentation/ |
| D | email-clients.txt | 19 attachments, but then the attachments should have content-type
20 "text/plain". However, attachments are generally frowned upon because
136 You can safely GPG sign attachments, but inlined text is preferred for
140 If you absolutely must send patches as attachments instead of inlining
200 - Works well for inlining text (or using attachments).
|
| D | dma-buf-sharing.txt | 108 the list of all attachments to a buffer.
137 scan through the list of attachments for this buffer, collate the requirements
|
| D | HOWTO | 409 want to deal with attachments or compressed patches; they may want
|
| D | SubmittingPatches | 333 6) No MIME, no links, no compression, no attachments. Just plain text.
|
| /linux-4.1.27/include/linux/ |
| D | dma-buf.h | 125 struct list_head attachments; member
|
| /linux-4.1.27/drivers/dma-buf/ |
| D | dma-buf.c | 334 INIT_LIST_HEAD(&dmabuf->attachments); in dma_buf_export()
441 list_add(&attach->node, &dmabuf->attachments); in dma_buf_attach()
805 list_for_each_entry(attach_obj, &buf_obj->attachments, node) { in dma_buf_describe()
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 146 Also, the system.mhs file defines bus attachments from the processor
148 attachments. Again an example; this system.mhs fragment:
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 5.Posting | 250 attachments; that makes it much harder for reviewers to quote sections of
|
| /linux-4.1.27/Documentation/s390/ |
| D | cds.txt | 111 peripheral attachments like disk devices (aka. DASDs), tapes, communication
|