From: Dave Jones <davej@redhat.com>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
len.brown@intel.com
Subject: Re: patch [0/2]: acpi: add generic removable drive bay support
Date: Fri, 8 Sep 2006 16:33:10 -0400 [thread overview]
Message-ID: <20060908203310.GM28592@redhat.com> (raw)
In-Reply-To: <20060908132123.16137ea3.kristen.c.accardi@intel.com>
On Fri, Sep 08, 2006 at 01:21:23PM -0700, Kristen Carlson Accardi wrote:
> On Fri, 8 Sep 2006 20:58:42 +0100
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>
> > On Thu, Sep 07, 2006 at 04:13:05PM -0700, Kristen Carlson Accardi wrote:
> >
> > Firstly, thanks for this - I wrote some related code a while ago. A
> > couple of questions...
> >
> > > can then be used by udev to unmount or rescan depending on the event. It will
> > > create a proc entry under /proc/acpi/bay for "eject" and for "status". Writing
> >
> > Do we really want it under /proc? It would seem to make more sense for
> > it to be under /sys.
>
> I agree - this is under proc because this is an acpi driver, and the acpi
> subsystem is still using the /proc fs for driver/user space interface. I
> thought I would just conform to their standard.
It's my understanding from talking with Len that he'd like to see /proc/acpi/
go away over time, so adding more to it seems to be at odds with that goal.
Dave
next prev parent reply other threads:[~2006-09-08 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 23:13 patch [0/2]: acpi: add generic removable drive bay support Kristen Carlson Accardi
2006-09-08 1:34 ` Nigel Cunningham
2006-09-08 17:48 ` Kristen Carlson Accardi
2006-09-08 19:59 ` Matthew Garrett
2006-09-08 19:58 ` Matthew Garrett
2006-09-08 20:21 ` Kristen Carlson Accardi
2006-09-08 20:33 ` Dave Jones [this message]
2006-10-14 5:13 ` Len Brown
2006-09-08 20:42 ` Matthew Garrett
2006-09-09 15:15 ` Alan Cox
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=20060908203310.GM28592@redhat.com \
--to=davej@redhat.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 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.