From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Sysfs and suicidal attributes
Date: Tue, 10 Jul 2007 11:04:47 +0200 [thread overview]
Message-ID: <20070710110447.0f63baf3@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <46934821.5020409@gmail.com>
On Tue, 10 Jul 2007 17:49:37 +0900,
Tejun Heo <htejun@gmail.com> wrote:
> What I was trying to say was that suicide and murder could be done the
> same way from the driver's POV or am I misunderstanding?
Do you mean a device unregistering itself from its attribute vs. a
device unregistering another device from its attribute?
>
> > A general immediate disconnect of the buffers (which will be handled in
> > a second pass) would be great, but doesn't sound easy.
>
> I haven't thought too hard about actual implementation but it's pretty
> specific case. If doing things in generic manner is difficult, there
> are plenty of shortcuts to choose from, I think.
The "second pass" approach where the store method calls the sysfs core
or sets a flag or whatever sounds doable, but I'm not sure how general
we can get. Maybe for all store methods that just trigger an action.
next prev parent reply other threads:[~2007-07-10 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 14:31 Alan Stern
2007-07-09 15:26 ` Cornelia Huck
2007-07-09 22:28 ` Alan Stern
2007-07-10 5:09 ` Tejun Heo
2007-07-10 8:28 ` Cornelia Huck
2007-07-10 8:49 ` Tejun Heo
2007-07-10 9:04 ` Cornelia Huck [this message]
2007-07-10 9:13 ` Tejun Heo
2007-07-10 10:50 ` Cornelia Huck
2007-07-10 14:42 ` Alan Stern
2007-07-10 14:41 ` Alan Stern
2007-07-10 15:11 ` Tejun Heo
2007-07-10 17:18 ` Alan Stern
2007-07-10 18:08 ` Tejun Heo
2007-07-10 19:31 ` Alan Stern
2007-07-11 5:04 ` Tejun Heo
2007-07-11 12:36 ` Cornelia Huck
2007-07-11 15:04 ` Alan Stern
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=20070710110447.0f63baf3@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®