Home
last modified time | relevance | path

Searched full:concrete (Results 1 – 25 of 41) sorted by relevance

12

/linux-6.12.1/rust/helpers/
Dbuild_assert.c10 * single object). Most modern platforms use the same concrete integer type for
/linux-6.12.1/rust/kernel/sync/arc/
Dstd_vendor.rs12 /// Attempt to downcast the `Arc<dyn Any + Send + Sync>` to a concrete type.
/linux-6.12.1/Documentation/driver-api/
Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
/linux-6.12.1/arch/riscv/include/asm/
Dbarrier.h52 * any concrete reason we need a full IO fence, it seems safer to just upgrade
/linux-6.12.1/Documentation/usb/
Draw-gadget.rst10 any concrete USB functions itself but requires userspace to do that.
/linux-6.12.1/drivers/media/test-drivers/vidtv/
Dvidtv_encoder.h100 * @id: So we can cast to a concrete implementation when needed.
/linux-6.12.1/fs/notify/fanotify/
Dfanotify.h235 * Common structure for fanotify events. Concrete structs are allocated in
238 * be freed and which concrete struct it may be cast to.
/linux-6.12.1/rust/macros/
Dpin_data.rs21 // concrete name. in pin_data()
/linux-6.12.1/Documentation/devicetree/bindings/interrupt-controller/
Dsifive,plic-1.0.0.yaml39 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
/linux-6.12.1/drivers/tty/
Dtty_port.c134 * to a concrete tty specified by @index. Use this or tty_port_install() (or
155 * linked to a concrete tty specified by @index. Use this or tty_port_install()
735 * to a concrete tty specified by @tty. Use this or tty_port_register_device()
/linux-6.12.1/drivers/gpu/drm/amd/amdkfd/
Dkfd_mqd_manager.h38 * @load_mqd: Loads the mqd to a concrete hqd slot. Used only for no cp
Dkfd_device_queue_manager.h235 * concrete device. This class is the only class in the queues scheduler
Dkfd_mqd_manager_cik.c323 * HIQ MQD Implementation, concrete implementation for HIQ MQD implementation.
/linux-6.12.1/drivers/net/ethernet/qlogic/qed/
Dqed_hw.h252 * qed_vfid_to_concrete(): Build a concrete FID for a given VF ID
Dqed.h878 * the concrete value.
881 * @concrete_fid: Concrete fid.
/linux-6.12.1/Documentation/filesystems/
Djournalling.rst176 The journalling layer uses typedefs to 'hide' the concrete definitions
/linux-6.12.1/include/linux/
Dbpf_mprog.h16 * no relative object was specified, see corresponding selftests for concrete
/linux-6.12.1/drivers/staging/fbtft/
Dfb_st7789v.c138 * Nonetheless, this sequence can be used as a template for concrete
/linux-6.12.1/Documentation/process/
Dbackporting.rst537 One concrete example of this was a pair of patches to the system call
600 For a more concrete example, see this video tutorial where two patches
/linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/
Den_stats.h136 /* Concrete NIC Stats */
/linux-6.12.1/drivers/i2c/busses/
Di2c-iop3xx.c190 * Concrete compare_funcs
/linux-6.12.1/include/linux/qed/
Dcommon_hsi.h1152 /* Concrete Function ID */
1167 /* Concrete Function ID */
/linux-6.12.1/tools/lib/bpf/
Dlinker.c88 * rewriting types when extern VAR/FUNC is resolved to a concrete
1354 /* validate if FWD kind matches concrete kind */ in glob_sym_btf_matches()
1360 pr_warn("global '%s': incompatible %s forward declaration and concrete kind %s\n", in glob_sym_btf_matches()
1367 pr_warn("global '%s': incompatible %s forward declaration and concrete kind %s\n", in glob_sym_btf_matches()
1646 * concrete map definition exactly. This restriction might be lifted in glob_map_defs_match()
/linux-6.12.1/Documentation/fb/
Dframebuffer.rst100 thus doesn't need to know, for example, how the color registers of the concrete
/linux-6.12.1/drivers/usb/gadget/legacy/
DKconfig524 implement any concrete USB functions itself but requires userspace

12