public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: patch [0/2]: acpi: add generic removable drive bay support
Date: Sat, 14 Oct 2006 01:13:37 -0400	[thread overview]
Message-ID: <200610140113.37934.len.brown@intel.com> (raw)
In-Reply-To: <20060908203310.GM28592@redhat.com>

On Friday 08 September 2006 16:33, Dave Jones wrote:
> 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:
>  > 
>  > > > 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 is right.  We've had a moratorium on new files under /proc/acpi for some time now.
The reason is that user-space should not know or care that something is supplied
by ACPI -- for on other systems it may be supplied by something else.

So new stuff should have generic names under sys -- even if on a large body of
systems the functionality beneath happens to be  supplied via ACPI.

an example of old is the brightness stuff under /proc/acpi and in various platform
specific drivers that scribble under /proc/acpi.
The corresponding example of new is the backlight I/F under /sys.

thanks,
-Len

  reply	other threads:[~2006-10-14  5:12 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
2006-10-14  5:13       ` Len Brown [this message]
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=200610140113.37934.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=davej@redhat.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=lenb@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox