On Mon, 2014-11-10 at 21:49 -0800, Joe Perches wrote: > 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@xxxxxxxxxx> > > > > Cc: Joe Perches <joe@xxxxxxxxxxx> > > > > --- > > > > 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@xxxxxxxxxx> > MAINTAINERS-L: autofs@xxxxxxxxxxxxxxx > 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 Oh, you meant what public tree. I guess I could make a kernel.org tree but, apart from this recent rename autofs4 -> autofs, the number of autofs changes hasn't warranted maintaining a separate tree for quite a while. It looks like the place holder under /pub/scm/linux/kernel/git/raven is no longer present so I expect I'd need to request that be setup. That's why I just send my patches to Andrew to include them in -next. Andrew, thoughts? Ian -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
