Home
last modified time | relevance | path

Searched refs:concrete (Results 1 – 8 of 8) sorted by relevance

/linux/rust/syn/
H A Dmacros.rs174 $vis:vis fn $name:ident $args:tt -> $impl_trait:ty [$concrete:ty] $body:block
178 $vis fn $name $args -> $concrete $body
/linux/Documentation/driver-api/
H A Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
/linux/Documentation/usb/
H A Draw-gadget.rst10 any concrete USB functions itself but requires userspace to do that.
/linux/Documentation/filesystems/
H A Djournalling.rst174 The journalling layer uses typedefs to 'hide' the concrete definitions
/linux/Documentation/security/
H A Dsnp-tdx-threat-model.rst44 While the concrete implementation details differ between technologies, all
/linux/Documentation/fb/
H A Dframebuffer.rst100 thus doesn't need to know, for example, how the color registers of the concrete
/linux/drivers/net/ethernet/qlogic/qed/
H A Dqed_sriov.c431 u32 concrete; in qed_iov_setup_vfdb() local
449 concrete = qed_vfid_to_concrete(p_hwfn, vf->abs_vf_id); in qed_iov_setup_vfdb()
450 vf->concrete_fid = concrete; in qed_iov_setup_vfdb()
/linux/drivers/usb/gadget/legacy/
H A DKconfig524 implement any concrete USB functions itself but requires userspace