Searched full:correspondence (Results 1 – 15 of 15) sorted by relevance
22 accessed via an ioport) and laid out with a direct correspondence to the
314 * The correspondence between bits and ports is
119 correspondence between VF netdevices and VF representors, more advanced device
91 multiple functions within the same object). There is a 1-1 correspondence
15 * correspondence between the two configurations.
54 correspondence between a PCIe RID (bus/dev/fn) with a PE number.
88 * has a direct correspondence, and needs to appear sufficiently aligned
53 For most cards, there is a one-to-one correspondence between outputs
1239 * It is temporary correspondence in arch_setup()
4763 * FWD -> STRUCT/UNION correspondence as well. FWD resolution is bidirectional:4766 * for struct/union correspondence mapping (described below), for FWD resolution4778 * correspondence between structs/unions.4780 * No canonical correspondence is derived for primitive types (they are already
44 * CORRESPONDENCE TO DESCRIPTION. THE ENTIRE RISK ARISING OUT OF USE OR
2036 * These commands have a 1:1 correspondence in acpi_nfit_register_dimms()
326 * There is no correspondence between an N-PORT id and an AL_PA. Therefore the
2368 * following the rules outlined below about u64/s64 correspondence in __reg32_deduce_bounds()2369 * (which equally applies to u32 vs s32 correspondence). In general it in __reg32_deduce_bounds()