From: Enrico Weigelt <weigelt@metux.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] device-core: sysfs open - close notify
Date: Tue, 16 Nov 2010 04:14:30 +0100 [thread overview]
Message-ID: <20101116031429.GA643@nibiru.local> (raw)
In-Reply-To: <1288679408.2080.18.camel@noppispoppis.nmp.nokia.com>
* Onkalo Samu <samu.p.onkalo@nokia.com> wrote:
<snip />
Perhaps it also could be an more generic event notification op,
where some event id or bitmask tells what actually happened ?
Something like:
...
void (*notify)(struct kobject *, struct attribute *, int event, void * param);
...
That would at least save one ptr of space and can be extended for
other stuff later.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
prev parent reply other threads:[~2010-11-16 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 12:46 [RFC PATCH] device-core: sysfs open - close notify Samu Onkalo
2010-10-31 16:14 ` Ming Lei
2010-11-01 17:11 ` Alan Cox
2010-11-02 6:30 ` Onkalo Samu
2010-11-16 3:14 ` Enrico Weigelt [this message]
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=20101116031429.GA643@nibiru.local \
--to=weigelt@metux.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).