Linux NILFS development
 help / color / mirror / Atom feed
From: Li Hong <lihong.hi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ryusuke Konishi
	<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 2/2] nilfs2: add a print message after loading nilfs2
Date: Fri, 9 Apr 2010 23:19:54 +0800	[thread overview]
Message-ID: <20100409151954.GB4582@xhl> (raw)
In-Reply-To: <20100409151837.GA4582@xhl>

From 7045703b978d8396535c7ccce72ca5684f608ca9 Mon Sep 17 00:00:00 2001
From: Li Hong <lihong.hi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Fri, 9 Apr 2010 23:09:53 +0800
Subject: [PATCH 2/2] nilfs2: add a print message after loading nilfs2

Printing a message after loading a file system is a practice. Add this to
provide a better user-friendly experience.

Signed-off-by: Li Hong <lihong.hi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
 fs/nilfs2/super.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/fs/nilfs2/super.c b/fs/nilfs2/super.c
index 51fd922..51f3802 100644
--- a/fs/nilfs2/super.c
+++ b/fs/nilfs2/super.c
@@ -1189,6 +1189,7 @@ static int __init init_nilfs_fs(void)
 	if (err)
 		goto free_cachep;
 
+	printk(KERN_INFO "NILFS version 2 loaded\n");
 	return 0;
 
 free_cachep:
-- 
1.6.3.3

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-09 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 15:18 [PATCH 1/2] nilfs2: cleanup multi kmem_cache_{create,destroy} code Li Hong
2010-04-09 15:19 ` Li Hong [this message]
2010-04-09 16:21 ` Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2010-04-05 17:34 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
     [not found]       ` <20100408.113405.221629738.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-08  5:45         ` Li Hong
     [not found]           ` <u2p3a3680031004072245t5ea476a5xbd6cbe6d3302de00-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-08  7:21             ` Ryusuke Konishi
     [not found]               ` <20100408.162141.218082254.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-04-08 15:47                 ` Li Hong

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=20100409151954.GB4582@xhl \
    --to=lihong.hi-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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