linux-kernel - Re: [PATCH 2/2] nilfs2: add a print message after loading nilfs2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 8 Apr 2010 13:45:05 +0800
From:	Li Hong <lihong.hi@...il.com>
To:	Ryusuke Konishi <ryusuke@...g.net>
Cc:	konishi.ryusuke@....ntt.co.jp, linux-nilfs@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] nilfs2: add a print message after loading nilfs2

2010/4/8 Ryusuke Konishi <ryusuke@...g.net>:
> On Wed, 7 Apr 2010 22:20:58 +0800, Li Hong <lihong.hi@...il.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".
Yes. I just thought that printing a message after loading a file
system is a practice.
You may choose any string that you think is suitable :)

> 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.
Ok. No problem.

> And, please include some explanation in the change log to clarify the
> aim or motivation.
I took it as a very simple patch and thought a header was enough. I can add more
explanations if here has a demand.

> Thanks,
> Ryusuke Konishi
>

Thanks very much,
Li Hong
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/