Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED
From: <hidden>
Date: 2015-02-27 16:31:58
Possibly related (same subject, not in this thread)
- 2015-03-03 · Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED · Josh Triplett <hidden>
- 2015-03-03 · Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED · Michael Kerrisk (man-pages) <hidden>
- 2015-03-02 · Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED · <hidden>
- 2015-02-27 · Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED · Michael Kerrisk (man-pages) <hidden>
- 2015-02-27 · [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED · Josh Triplett <hidden>
On Fri, Feb 27, 2015 at 07:42:44AM +0100, Michael Kerrisk (man-pages) wrote:
On 02/27/2015 01:41 AM, Josh Triplett wrote:quoted
Normally, system calls return EINVAL for flags they don't support. Explicitly document that clone does *not* produce an error for these two obsolete flags.Thanks, Josh! Applied.
Doesn't appear to be in the current git repository. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html