From: David Brownell <david-b@pacbell.net>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: 'Nick Bellinger' <nickb@attheoffice.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Patrick Mochel <mochel@osdl.org>
Subject: Re: driverfs is not for everything! (was: [PATCH] /proc/scsi/map )
Date: Mon, 24 Jun 2002 11:04:08 -0700 [thread overview]
Message-ID: <af7n24$1uf$2@main.gmane.org> (raw)
In-Reply-To: 59885C5E3098D511AD690002A5072D3C02AB7F53@orsmsx111.jf.intel.com
>>No, of course driverfs isn't for everything. But if it's not
>>for all drivers,
>>then what's it for -- just power management?
>
> "Just" power management??? Like power management isn't important enough???
> ;-)
Well, it's only one of the roles I'd expect of a "driver filesystem",
and actually no -- not the most important one. If instead it were
called "powermanagementfs" ... or if it were renamed to that ... :)
> We need a device tree to do PM. If driverfs's PM capabilities are hurt
> because it doesn't stay true to that, then the featureitis has gone too far.
And for other reasons, we also need one. I don't think you've actually
pointed out any concrete problems for PM though.
- Dave
next prev parent reply other threads:[~2002-06-24 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <andrew.grover@intel.com>
2002-06-24 17:35 ` driverfs is not for everything! (was: [PATCH] /proc/scsi/map ) Grover, Andrew
2002-06-24 18:04 ` David Brownell [this message]
2002-06-24 18:09 ` James Bottomley
2002-06-24 19:23 ` Oliver Xymoron
2002-06-25 18:38 ` Patrick Mochel
2002-06-24 18:32 ` Roman Zippel
2002-06-24 22:47 ` John Summerfield
2002-06-25 18:35 ` Patrick Mochel
2002-07-01 2:41 ` Pavel Machek
2002-06-24 18:47 Grover, Andrew
2002-06-24 19:03 ` Oliver Xymoron
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 18:37 Grover, Andrew
2002-06-23 22:59 driverfs is not for everything! (was: [PATCH] /proc/scsi/map) Grover, Andrew
2002-06-24 1:34 ` David Brownell
2002-06-24 5:18 ` Nick Bellinger
2002-06-24 6:41 ` Brad Hards
2002-06-25 18:18 ` Patrick Mochel
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='af7n24$1uf$2@main.gmane.org' \
--to=david-b@pacbell.net \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=nickb@attheoffice.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