Home
last modified time | relevance | path

Searched refs:followup (Results 1 – 5 of 5) sorted by relevance

/openbmc/linux/Documentation/process/
H A Dsecurity-bugs.rst58 and followup discussions (if any), exploits, CVE information or the
62 information submitted to the security list and any followup discussions
/openbmc/u-boot/common/
H A Dcli_hush.c260 pipe_style followup; /* PIPE_BG, PIPE_SEQ, PIPE_OR, PIPE_AND */ member
1724 if (interactive && pi->followup!=PIPE_BG) {
1817 if (pi->followup == PIPE_SEQ) flag_skip=0;
1881 } else if (pi->followup==PIPE_BG) {
1918 if ( (rcode==EXIT_SUCCESS && pi->followup==PIPE_OR) ||
1919 (rcode!=EXIT_SUCCESS && pi->followup==PIPE_AND) )
2009 final_printf("%s pipe followup code %d\n", ind, pi->followup);
2349 pi->followup = 0; /* invalid */
2595 ctx->pipe->followup = type;
/openbmc/linux/Documentation/userspace-api/
H A Dfutex2.rst14 futex2 is a followup version of the initial futex syscall, designed to overcome
/openbmc/bmcweb/
H A DCOMMON_ERRORS.md235 requests, the security scanner logs it as an error for followup. While in
/openbmc/qemu/docs/devel/
H A Dsubmitting-a-patch.rst472 fresh email or series of emails -- don't try to make it a followup to