[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1603230837420.10977@pianoman.cluster.toy>
Date: Wed, 23 Mar 2016 08:43:45 -0400 (EDT)
From: Vince Weaver <vince@...ter.net>
To: "Wangnan (F)" <wangnan0@...wei.com>
cc: Peter Zijlstra <peterz@...radead.org>, mingo@...hat.com,
linux-kernel@...r.kernel.org, He Kuang <hekuang@...wei.com>,
Alexei Starovoitov <ast@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Brendan Gregg <brendan.d.gregg@...il.com>,
Jiri Olsa <jolsa@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Zefan Li <lizefan@...wei.com>, pi3orama@....com,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Subject: Re: [PATCH 1/5] perf core: Introduce new ioctl options to pause and
resume ring buffer
On Wed, 23 Mar 2016, Wangnan (F) wrote:
>
> > Can you also do a patch to the man-pages?
> >
> > http://man7.org/linux/man-pages/man2/perf_event_open.2.html
>
> Sure.
>
> I think I need to provide a patch for:
>
> http://git.kernel.org/cgit/docs/man-pages/man-pages.git
>
> But which one should be the first? Shall we update man pages before
> this patch be merged by upstream? Or Michael and Vince will consider
> this problem?
It is good to see a rough draft of the manpage changes for an ABI
addition like this before the patch gets merged just so we can catch
anything odd about the interface.
Also include (as a comment) the git commit id that introduces the change.
In general manpage patches do not get committed until after the change
hits a full released kernel (as things have been known to get reverted
from -rc kernels in the past).
If you send a rough patch I can fix it up and queue it up with other
manpage patches I have (I'm a bit backlogged but working on catching up).
I'm never quite sure that I get all of the various Signed-off- lines right
for contributed patches though.
Vince
Powered by blists - more mailing lists