mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Pavel Machek <pavel@suse.cz>
Cc: mochel@osdl.org, greg@kroah.com, hannal@us.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFT/C 2.5.70] Input class hook up to driver model/sysfs
Date: Thu, 5 Jun 2003 15:56:42 -0700	[thread overview]
Message-ID: <20030605155642.68179245.akpm@digeo.com> (raw)
In-Reply-To: <20030605224535.GH608@elf.ucw.cz>

Pavel Machek <pavel@suse.cz> wrote:
>
> Hi!
> 
> > > Okay, that means that another patch is needed to create hierarchy for
> > > power managment... This sysfs stuff is getting hairy.
> > 
> > No it's not. The hierarchy is the device tree, which is the original 
> > purpose of it, remember? 
> 
> device tree is okay with me, but... it took quite a long patch to add
> it to classes. I thought that classes are only going to be symlinks
> into device tree, but this patch added classes without adding to the
> device tree...

Al Viro has asked that sysfs conversions such as this be placed on hold
until we sort through the newly-added bugs arising from the sysfsification
of netdevs and request queues.  

So yeah, do the work, but please make sure that you understand what went
wrong with netdevs and queues, and make sure that the input sysfsification
addresses those problems.  Preferably in the same way...


  reply	other threads:[~2003-06-05 22:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  1:04 Hanna Linder
2003-05-28 23:11 ` Hanna Linder
2003-05-29  7:30 ` Greg KH
2003-05-29  9:30 ` Christoph Hellwig
2003-06-05 21:12 ` Pavel Machek
2003-06-05 21:17   ` Greg KH
2003-06-05 22:07     ` Pavel Machek
2003-06-05 22:12       ` Patrick Mochel
2003-06-05 22:45         ` Pavel Machek
2003-06-05 22:56           ` Andrew Morton [this message]
2003-06-05 23:41             ` viro
2003-06-06  0:03               ` Hanna Linder
2003-06-05 22:16       ` Greg KH

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=20030605155642.68179245.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=greg@kroah.com \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@suse.cz \
    /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®