[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m163th6yz2.fsf@frodo.ebiederm.org>
Date: Wed, 14 May 2008 02:01:37 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Randy Dunlap <RANDY.DUNLAP@...CLE.COM>, Greg KH <greg@...ah.com>,
Al Viro <viro@....linux.org.uk>,
Benjamin Thery <benjamin.thery@...l.net>,
Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Daniel Lezcano <dlezcano@...ibm.com>,
Pavel Emelyanov <xemul@...nvz.org>,
"Serge E. Hallyn" <serue@...ibm.com>, Tejun Heo <htejun@...il.com>
Subject: Re: [PATCH] Fix kobject_rename and !CONFIG_SYSFS v4
Andrew Morton <akpm@...ux-foundation.org> writes:
>> diff --git a/include/linux/sysfs.h b/include/linux/sysfs.h
>> index 7858eac..6e61033 100644
>> --- a/include/linux/sysfs.h
>> +++ b/include/linux/sysfs.h
>> @@ -20,6 +20,8 @@
>> struct kobject;
>> struct module;
>>
>> +extern int kobject_set_name(struct kobject *kobj, const char *name, ...)
>> + __attribute__((format(printf, 2, 3)));
>
> Duplicating the kobject_set_name() declaration in sysfs.h is rather a hack.
A bit. It really isn't worse then a struct declaration like struct kobject;
> It'd be better to move it into a new header file, included by both
> sysfs.h and kobject.h. Perhaps there are other declarations which can
> be moved with it.
My gut feel says that sysfs.h should include kobject.h instead of the
other way around.
However it gets reorganized, it is an entirely separate problem
from the one this patch sets out to solve and so should go in
a different patch.
Eric
--
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/
Powered by blists - more mailing lists