Searched full:prep (Results 1 – 7 of 7) sorted by relevance
1436 * ``int (*preparse)(struct key_preparsed_payload *prep);``1440 instantiate key). The structure pointed to by prep looks like::1468 * ``void (*free_preparse)(struct key_preparsed_payload *prep);``1477 * ``int (*instantiate)(struct key *key, struct key_preparsed_payload *prep);``1483 The prep->data and prep->datalen fields will define the original payload1496 prep->payload.data[] to key->payload.data[], with RCU-safe assignment on1497 the first element. It will then clear prep->payload.data[] so that the1506 The prep->data and prep->datalen fields will define the original payload
77 ..__[EXEC]__|__[PREP]__|__[ENTRY]__|__[IDLE]__|__[EXIT]__|__[EXEC]__..91 PREP: Preparation phase before committing the hardware to idle mode132 has not expired. The abortable nature of the PREP period can be ignored133 if it cannot be relied upon (e.g. the PREP deadline may occur much sooner than421 PREP phase (see diagram 1, section 2) is non-neglibigle. In such
263 int (*parse)(struct key_preparsed_payload *prep);
159 (code obtained from prep.ai.mit.edu)
305 └─ [PATCH net-next 1/3] net: some feature prep
65 and ``-3``/``--prep-3way`` to do some of this automatically (see the
2467 <https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-prep-for-bulk-l…2848 <https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-prep-for-bulk-l…