From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: tom.leiming@gmail.com
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
Ming Lei <tom.leiming@gmail.com>
Subject: Re: [PATCH] driver core: implement uevent suppress in kobject(v1)
Date: Mon, 2 Mar 2009 18:51:25 +0100 [thread overview]
Message-ID: <20090302185125.5038a705@gondolin> (raw)
In-Reply-To: <1235913049-4533-1-git-send-email-tom.leiming@gmail.com>
On Sun, 1 Mar 2009 21:10:49 +0800,
tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>
>
> This patch implements uevent suppress in kobject and removes it
> from struct device, based on the following ideas:
>
> 1,Uevent sending should be one attribute of kobject, so suppressing it
> in kobject layer is more natural than in device layer. By this way,
> we can do it for other objects embedded with kobject.
>
> 2,It may save several bytes for each instance of struct device.(On my
> omap3(32bit ARM) based box, can save 8bytes per device object)
>
> This patch also introduces dev_set|get_uevent_suppress() helpers to
> set and query uevent_suppress attribute in case to help kobject
> as private part of struct device in future.
But moving the kobject into an allocated private structure would be
rather broken?
I have no objections to the patch, though, and it worked fine on my
s390 LPAR.
>
> [This version is against the latest driver-core patch set of Greg,please
> ignore the last version.]
>
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
next prev parent reply other threads:[~2009-03-02 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 15:25 [PATCH] driver core: implement uevent suppress in kobject tom.leiming
2009-03-01 13:10 ` [PATCH] driver core: implement uevent suppress in kobject(v1) tom.leiming
2009-03-02 17:51 ` Cornelia Huck [this message]
2009-03-02 18:23 ` Greg KH
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=20090302185125.5038a705@gondolin \
--to=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.