From: Joe Perches <joe@perches.com>
To: Ian Kent <raven@themaw.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] autofs - fix log print messages
Date: Mon, 10 Nov 2014 21:49:49 -0800 [thread overview]
Message-ID: <1415684989.16070.2.camel@perches.com> (raw)
In-Reply-To: <1415684245.2486.9.camel@perseus.themaw.net>
On Tue, 2014-11-11 at 13:37 +0800, Ian Kent wrote:
> On Mon, 2014-11-10 at 19:25 -0800, Joe Perches wrote:
> > On Tue, 2014-11-11 at 09:29 +0800, Ian Kent wrote:
> > > Fix some inconsistencies in log print output and ensure that
> > > the module name is included in all log prints.
> > >
> > > Signed-off-by: Ian Kent <raven@themaw.net>
> > > Cc: Joe Perches <joe@perches.com>
> > > ---
> > > fs/autofs/autofs_i.h | 6 +++---
> > > fs/autofs/dev-ioctl.c | 2 +-
> > > fs/autofs/inode.c | 10 +++++-----
> > > fs/autofs/waitq.c | 4 ++--
> > > 4 files changed, 11 insertions(+), 11 deletions(-)
> >
> > What tree are these patches made against?
>
> They live in an StGit patch queue against the current Linus tree.
> They depend on the prior series to rename autofs4 to autofs.
Hey Ian.
Maybe you could add the git tree location to
the MAINTAINERS entry:
MAINTAINERS-KERNEL AUTOMOUNTER v4 (AUTOFS4)
MAINTAINERS-M: Ian Kent <raven@themaw.net>
MAINTAINERS-L: autofs@vger.kernel.org
MAINTAINERS-S: Maintained
MAINTAINERS:F: fs/autofs4/
T: git git://somewhere_or_other...
and maybe you also could get Stephen Rothwell
to add that tree to -next
next prev parent reply other threads:[~2014-11-11 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 1:29 [PATCH 1/3] autofs - fix log print messages Ian Kent
2014-11-11 1:30 ` [PATCH 2/3] autofs - change log prints to not insert newline Ian Kent
2014-11-11 1:30 ` [PATCH 3/3] autofs - use pr_xxx() calls directly for logging Ian Kent
2014-11-11 3:25 ` [PATCH 1/3] autofs - fix log print messages Joe Perches
2014-11-11 5:37 ` Ian Kent
2014-11-11 5:49 ` Joe Perches [this message]
2014-11-11 6:01 ` Ian Kent
2014-11-12 23:07 ` Andrew Morton
2014-11-13 0:10 ` Ian Kent
2014-11-13 3:50 ` Ian Kent
2014-11-11 6:07 ` Ian Kent
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=1415684989.16070.2.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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