On Wed, Mar 13, 2013 at 9:05 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Mar 13, 2013 at 08:47:14PM +0100, Sedat Dilek wrote:
>>
>> Signed-off-by: Sedat Dilek <sedat.dilek@xxxxxxxxx>
>> ---
>> fs/overlayfs/super.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
>> index 482c26f..e30141f 100644
>> --- a/fs/overlayfs/super.c
>> +++ b/fs/overlayfs/super.c
>> @@ -674,6 +674,8 @@ MODULE_ALIAS_FS("overlayfs");
>>
>> static int __init ovl_init(void)
>> {
>> + printk(KERN_INFO "overlayfs: loaded\n");
>> +
>
> Could we please create a new maillist for that kind of stuff? It's seriously
> overdue, IMO. linux-bikeshedding@xxxxxxxxxxxxxxx, if davem doesn't mind
> touching that...
Dear Mr. Viro,
I looked over fs/ especially in concerńs of status-informations - I
had better not done it.
This remembered me the crap with drm/kms with all its useless driver info.
Here for you:
[ 10.998890] [drm] Initialized drm 1.1.0 20060810
[ 13.147821] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
( On a quick Google search I found [1] (I rememebr there were 4
patches but break user-space as there exists kernel-drm and libdrm). )
As an enduser I want some useful help.
As a non-native English I had to look up that "bikeshedding" word.
People asked for review why not test it and give feedback - even
report on useless stuff seen from your POV.
This might be a little detail in your eyes - but you are free to have
a deeper look on overlayfs as an filesystem-expert.
For me it is important that this drama comes to an end.
O.O. drama - isn't someone dying in the end :-).
Take it with British humour :-).
- Sedat -
[1] https://lkml.org/lkml/2010/12/22/50
--
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
