From: Arnd Bergmann <arnd@arndb.de>
To: Paul Bolle <pebolle@tiscali.nl>, mtk.manpages@gmail.com
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees.cook@canonical.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Export linux/syslog.h
Date: Mon, 7 Feb 2011 15:33:37 +0100 [thread overview]
Message-ID: <201102071533.37755.arnd@arndb.de> (raw)
In-Reply-To: <1297084682.1741.17.camel@t41.thuisdomein>
On Monday 07 February 2011, Paul Bolle wrote:
> > Further, the man page currently documents the raw numbers and should
> > be changed as well with the new constants.
>
> Yes, I realized that. I assumed that updating the man page should be
> done after this patch was accepted. Or should patches like this one be
> done in parallel with the patch(es) to the relevant man page(s)? Either
> way is fine with me.
I would recommend sending both patches together for review, though the
man page change will not be in a release before the kernel gets released
with your patch.
Arnd
prev parent reply other threads:[~2011-02-07 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:51 [PATCH] Export linux/syslog.h Paul Bolle
2011-02-07 12:55 ` Arnd Bergmann
2011-02-07 13:17 ` Paul Bolle
2011-02-07 14:33 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201102071533.37755.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=pebolle@tiscali.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox