Date: Wed, 22 Apr 2015 21:01:34 +0000 (UTC)
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: mtk manpages <mtk.manpages@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>, lkml <linux-kernel@vger.kernel.org>,
        Josh Triplett <josh@joshtriplett.org>,
        KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Nicholas Miell <nmiell@comcast.net>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Ingo Molnar <mingo@redhat.com>, Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
        Lai Jiangshan <laijs@cn.fujitsu.com>,
        Stephen Hemminger <stephen@networkplumber.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Peter Zijlstra <peterz@infradead.org>,
        David Howells <dhowells@redhat.com>,
        Pranith Kumar <bobby.prani@gmail.com>
Message-ID: <249593479.34550.1429736494057.JavaMail.zimbra@efficios.com>
In-Reply-To: <CAKgNAkh4boES3SK38KFKkC9WQZ_k_GuDns8tj_KqqWHPg-z6MQ@mail.gmail.com>
References: <1429283202-6245-1-git-send-email-mathieu.desnoyers@efficios.com> <1429633790.10273.2.camel@stgolabs.net> <1439042160.34486.1429731801901.JavaMail.zimbra@efficios.com> <CAKgNAkh4boES3SK38KFKkC9WQZ_k_GuDns8tj_KqqWHPg-z6MQ@mail.gmail.com>
Subject: Re: [PATCH v16] sys_membarrier(): system-wide memory barrier
 (generic, x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: sys_membarrier(): system-wide memory barrier (generic, x86)
Thread-Index: /FzunmOOOH09B2Gb7XvPTRTj3C0LqQ==
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1264
Lines: 38

----- Original Message -----
> On 22 April 2015 at 21:43, Mathieu Desnoyers
> <mathieu.desnoyers@efficios.com> wrote:
> > ----- Original Message -----
> >> On Fri, 2015-04-17 at 11:06 -0400, Mathieu Desnoyers wrote:
> >> > [ Not in this patch: tests (Pranith Kumar has a patch for this), man
> >> > page.
> >> > ]
> >>
> >> Actually, we had discussed that for new syscalls, the changelog _would_
> >> be the manpage -- at least included in it.
> >
> > Do you want the formatted content, or just the text ? Putting
> > manpage formatting in the changelog seems a bit odd.
> 
> 
> Plain text works for me. Just divide it up into the usuual man-pages
> sections (see man-pages(7), and I'll take care of the rest).

OK. Should I do the writeup as a man(2) from the POV of a glibc
user ? It's a bit different when we get to return values and
error codes if we document kernel<->glibc or glibc<->user.

Moreover, how can we get this into glibc ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/