From: Ryusuke Konishi <ryusuke@osrg.net>
To: lihong.hi@gmail.com
Cc: konishi.ryusuke@lab.ntt.co.jp, linux-nilfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] nilfs2: add a print message after loading nilfs2
Date: Thu, 08 Apr 2010 11:34:05 +0900 (JST) [thread overview]
Message-ID: <20100408.113405.221629738.ryusuke@osrg.net> (raw)
In-Reply-To: <20100407142058.GA27224@xhl>
On Wed, 7 Apr 2010 22:20:58 +0800, Li Hong <lihong.hi@gmail.com> wrote:
> Hi KONISHI Ryusuke,
>
> Any feedbacks on these patches?
>
> Thanks,
> Li Hong
Well, adding a load message is ok, but it should be more moderate like
"nilfs2 file system loaded\n".
I think this sort of change should be discussed in the sub topic
mailing list (i.e. linux-nilfs). You don't have to cc every patch to
linux-kernel.
And, please include some explanation in the change log to clarify the
aim or motivation.
Thanks,
Ryusuke Konishi
> On Tue, Apr 06, 2010 at 01:35:34AM +0800, Li Hong wrote:
> > From b4e426f77cd05bd6046c1fa67c51ee06368ea23e Mon Sep 17 00:00:00 2001
> > From: Li Hong <lihong.hi@gmail.com>
> > Date: Tue, 6 Apr 2010 01:23:04 +0800
> > Subject: [PATCH] nilfs2: add a print message after loading nilfs2
> >
> >
> > Signed-off-by: Li Hong <lihong.hi@gmail.com>
> > ---
> > fs/nilfs2/super.c | 7 ++++++-
> > 1 files changed, 6 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/nilfs2/super.c b/fs/nilfs2/super.c
> > index 2e767bc..9f91765 100644
> > --- a/fs/nilfs2/super.c
> > +++ b/fs/nilfs2/super.c
> > @@ -1186,7 +1186,12 @@ static int __init init_nilfs_fs(void)
> > return err;
> >
> > err = register_filesystem(&nilfs_fs_type);
> > - return err;
> > + if (err)
> > + return err;
> > +
> > + printk(KERN_INFO "nilfs2 file system loaded!\n");
printk(KERN_INFO "nilfs2 file system loaded!\n");
> > + return 0;
> > +
> > }
> >
> > static void __exit exit_nilfs_fs(void)
> > --
> > 1.6.3.3
> >
> --
> 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/
next prev parent reply other threads:[~2010-04-08 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 17:34 [PATCH 1/2] nilfs2: cleanup multi kmem_cache_{create,destroy} code Li Hong
2010-04-05 17:35 ` [PATCH 2/2] nilfs2: add a print message after loading nilfs2 Li Hong
2010-04-07 14:20 ` Li Hong
2010-04-08 2:34 ` Ryusuke Konishi [this message]
2010-04-08 5:45 ` Li Hong
2010-04-08 4:44 ` [PATCH 1/2] nilfs2: cleanup multi kmem_cache_{create,destroy} code Ryusuke Konishi
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=20100408.113405.221629738.ryusuke@osrg.net \
--to=ryusuke@osrg.net \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=lihong.hi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
/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
all inboxes | Powered by JetHome®