| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yasm/yasm/ |
| H A D | 0001-yasm-Set-build-date-to-SOURCE_DATE_EPOCH.patch | 33 # Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | w1.rst | 53 W1 external netlink API structures and commands.
|
| H A D | firewire.rst | 19 Firewire char device data structures
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt.rst | 10 struct :c:type:`v4l2_pix_format_mplane` structures define the
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/lxdm/lxdm/ |
| H A D | 0003-check-for-libexecinfo-providing-backtrace-APIs.patch | 34 # Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/openbmc/poky/meta/recipes-multimedia/libtiff/tiff/ |
| H A D | CVE-2023-6277-At-image-reading-compare-data-size-of-some-tags-data-2.patch | 5 structures (StripByteCounts, StripOffsets, StripArray, TIFF directory) with
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/concurrencykit/ |
| H A D | concurrencykit_git.bb | 2 safe memory reclamation mechanisms and non-blocking data structures \
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | drm-kms.rst | 248 back changes in data structures all over the place is hard to get right.
258 - The overall state is split up into per-object state structures:
263 can subclass these structures through embedding, or add entirely new state
264 structures for their globally shared hardware functions, see :c:type:`struct
268 of structures within the :c:type:`drm_atomic_state <drm_atomic_state>`
269 container. Driver private state structures are also tracked in the same
274 Locking of atomic state structures is internally using :c:type:`struct
|
| /openbmc/linux/Documentation/locking/ |
| H A D | robust-futex-ABI.rst | 48 kernel, then it can actually have two such structures - one using 32 bit
103 larger, user level locking structures, one per lock. The kernel
123 There may exist thousands of futex lock structures in a threads shared
124 memory, on various data structures, at a given point in time. Only those
125 lock structures for locks currently held by that thread should be on
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | device.rst | 75 This declares two structures of type struct device_attribute with respective
95 above two structures can be declared using:::
|
| H A D | driver.rst | 10 Device drivers are statically allocated structures. Though there may
45 The most common example of this are device ID structures. A driver
47 of these structures and the semantics for comparing device IDs are
49 sacrifice type-safety, so we keep bus-specific structures around.
160 it's a version the driver can handle, that driver data structures can
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/ |
| H A D | libxml-simple-perl_2.25.bb | 5 (by Grant McLean) to use the XML::LibXML parser for XML structures, \
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/openl2tp/openl2tp/ |
| H A D | 0002-user-ipv6-structures.patch | 4 Subject: [PATCH 2/2] user ipv6 structures
|
| /openbmc/linux/Documentation/mhi/ |
| H A D | mhi.rst | 47 Data structures
50 All data structures used by MHI are in the host system memory. Using the
51 physical interface, the device accesses those data structures. MHI data
52 structures and data buffers in the host system memory regions are mapped for
|
| /openbmc/openbmc/poky/meta/recipes-bsp/lrzsz/lrzsz-0.12.20/ |
| H A D | lrzsz-check-locale.h.patch | 28 dnl Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/inarp/ |
| H A D | configure.ac | 18 # Checks for typedefs, structures, and compiler characteristics.
|
| /openbmc/openbmc/poky/meta/recipes-gnome/json-glib/ |
| H A D | json-glib_1.8.0.bb | 3 data structures, using a DOM-like API. JSON-GLib also offers GObject \
|
| /openbmc/linux/Documentation/mm/ |
| H A D | index.rst | 36 structures and algorithms. It should all be integrated nicely into the
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0026-nvmxip-move-header-to-include.patch | 7 to get the internal bdev structures to access
|
| H A D | 0022-fwu_metadata-make-sure-structures-are-packed.patch | 4 Subject: [PATCH] fwu_metadata: make sure structures are packed
|
| /openbmc/linux/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 9 sometimes tempted to use it in kernel code when shared data structures are
16 do. In the kernel, one must protect shared data structures against
92 - Pointers to data structures in coherent memory which might be modified
|
| /openbmc/linux/Documentation/security/ |
| H A D | lsm.rst | 32 kernel data structures for maintaining security attributes. This
60 The LSM framework includes security fields in kernel data structures and
117 and free security structures for inode objects.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | of-plat.txt | 21 It is possible to create platform data manually by defining C structures
47 included in the structures since there is generally no mention of it
65 out this code, since the structures are only available in SPL.
216 * the device tree (or the C structures when of-platdata is used).
240 /* Decode the of-platdata from the C structures */
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/poke/ |
| H A D | poke_1.2.bb | 3 …procedural, interactive programming language designed to describe data structures and to operate o…
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-lefi-boardinfo | 10 The related structures are already defined in the interface
|