Home
last modified time | relevance | path

Searched refs:attachments (Results 1 – 24 of 24) sorted by relevance

/kernel/linux/linux-5.10/tools/bpf/bpftool/Documentation/
Dbpftool-net.rst5 tool for inspection of netdev/tc related bpf prog attachments
34 List bpf program attachments in the kernel networking subsystem.
36 Currently, only device driver xdp attachments and tc filter
37 classification/action attachments are implemented, i.e., for
43 users can use **bpftool cgroup** to dump cgroup attachments.
47 The current output will start with all xdp program attachments, followed by
48 all tc class/qdisc bpf program attachments. Both xdp programs and
Dbpftool-perf.rst5 tool for inspection of perf related bpf prog attachments
/kernel/linux/linux-5.10/drivers/dma-buf/heaps/
Dheap-helpers.c24 INIT_LIST_HEAD(&buffer->attachments); in init_heap_helper_buffer()
119 list_add(&a->list, &buffer->attachments); in dma_heap_attach()
210 list_for_each_entry(a, &buffer->attachments, list) { in dma_heap_dma_buf_begin_cpu_access()
230 list_for_each_entry(a, &buffer->attachments, list) { in dma_heap_dma_buf_end_cpu_access()
Dheap-helpers.h41 struct list_head attachments; member
/kernel/linux/linux-5.10/drivers/staging/android/ion/
Dion.c75 INIT_LIST_HEAD(&buffer->attachments); in ion_buffer_create()
205 list_add(&a->list, &buffer->attachments); in ion_dma_buf_attach()
303 list_for_each_entry(a, &buffer->attachments, list) in ion_dma_buf_begin_cpu_access()
324 list_for_each_entry(a, &buffer->attachments, list) in ion_dma_buf_end_cpu_access()
Dion.h52 struct list_head attachments; member
/kernel/linux/linux-5.10/Documentation/process/
Demail-clients.rst23 attachments, but then the attachments should have content-type
24 ``text/plain``. However, attachments are generally frowned upon because
152 You can safely GPG sign attachments, but inlined text is preferred for
156 If you absolutely must send patches as attachments instead of inlining
266 - Works well for inlining text (or using attachments).
D5.Posting.rst272 attachments; that makes it much harder for reviewers to quote sections of
Dhowto.rst420 attachments or compressed patches; they may want to comment on
Dsubmitting-patches.rst279 No MIME, no links, no compression, no attachments. Just plain text
/kernel/linux/linux-5.10/drivers/dma-buf/
Ddma-buf.c85 WARN_ON(!list_empty(&dmabuf->attachments)); in dma_buf_release()
355 if (!list_empty(&dmabuf->attachments)) { in dma_buf_set_name()
592 INIT_LIST_HEAD(&dmabuf->attachments); in dma_buf_export()
737 list_add(&attach->node, &dmabuf->attachments); in dma_buf_dynamic_attach()
992 list_for_each_entry(attach, &dmabuf->attachments, node) in dma_buf_move_notify()
1362 list_for_each_entry(attach_obj, &buf_obj->attachments, node) { in dma_buf_debug_show()
/kernel/linux/linux-5.10/include/linux/
Ddma-buf.h313 struct list_head attachments; member
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dsecurity-bugs.rst29 Please send plain text emails without attachments where possible.
31 issue if all the details are hidden away in attachments. Think of it like a
/kernel/linux/patches/linux-5.10/zhiyuan_patch/
Dkernel.patch158 INIT_LIST_HEAD(&dmabuf->attachments);
691 + struct list_head attachments;
735 + list_add(&a->list, &buffer->attachments);
794 + list_for_each_entry(a, &buffer->attachments, list) {
814 + list_for_each_entry(a, &buffer->attachments, list) {
966 + INIT_LIST_HEAD(&buffer->attachments);
1630 + struct list_head attachments;
1734 + list_add(&a->list, &buffer->attachments);
1809 + list_for_each_entry(a, &buffer->attachments, list) {
1832 + list_for_each_entry(a, &buffer->attachments, list) {
[all …]
/kernel/linux/linux-5.10/drivers/misc/
Dfastrpc.c150 struct list_head attachments; member
309 INIT_LIST_HEAD(&buf->attachments); in fastrpc_buf_alloc()
580 list_add(&a->node, &buffer->attachments); in fastrpc_dma_buf_attach()
/kernel/linux/linux-5.10/Documentation/trace/coresight/
Dcoresight-ect.rst43 no programmed trigger/channel attachments, so will not affect the system
/kernel/linux/linux-5.10/Documentation/s390/
Dvfio-ccw.rst69 different peripheral attachments like disk devices (aka. DASDs), tapes,
Dcds.rst118 peripheral attachments like disk devices (aka. DASDs), tapes, communication
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_cs.c421 list_empty(&bo->tbo.base.dma_buf->attachments))) { in amdgpu_cs_bo_validate()
/kernel/linux/linux-5.10/Documentation/virt/uml/
Duser_mode_linux_howto_v2.rst1079 Note - the list does not accept HTML or attachments, all emails must
/kernel/linux/patches/linux-5.10/yangfan_patch/
Ddrivers.patch6230 + struct list_head attachments;
6274 + list_add(&a->list, &buffer->attachments);
6331 + list_for_each_entry(a, &buffer->attachments, list) {
6351 + list_for_each_entry(a, &buffer->attachments, list) {
6503 + INIT_LIST_HEAD(&buffer->attachments);
6633 + struct list_head attachments;
6736 + list_add(&a->list, &buffer->attachments);
6811 + list_for_each_entry(a, &buffer->attachments, list) {
6834 + list_for_each_entry(a, &buffer->attachments, list) {
7048 + INIT_LIST_HEAD(&buffer->attachments);
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/
D0005_linux_include.patch16217 + attachments for the same header, …
19518 + attachments exists for the same header,
/kernel/linux/patches/linux-5.10/unionpi_tiger_pacth/
Dlinux-5.10.patch31096 + * map the same scatter list to multiple attachments at the same time.
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/
D0038_linux_drivers_mxc.patch137470 + list_for_each_entry(attach_obj, &buf_obj->attachments, node) {