mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	axboe@kernel.dk
Subject: Re: [PATCH] SYSFS: Allow boot time switching between deprecated and modern sysfs layout v2
Date: Tue, 21 Sep 2010 13:26:21 -0700	[thread overview]
Message-ID: <20100921202621.GA25112@kroah.com> (raw)
In-Reply-To: <20100908193910.2d27a33b@basil.nowhere.org>

On Wed, Sep 08, 2010 at 07:39:10PM +0200, Andi Kleen wrote:
> On Wed, 8 Sep 2010 17:27:37 +0200
> Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > On Wed, Sep 8, 2010 at 16:54, Andi Kleen <andi@firstfloor.org> wrote:
> > > From: Andi Kleen <ak@linux.intel.com>
> > >
> > > I have some systems which need legacy sysfs due to old udev
> > > versions, and it's a big hazzle to compile separate kernels for
> > > them.
> > 
> > It's not udev, it's other tools making wrong assumptions like that
> > directories can not be a symlink to a directory, or that a device is
> > always the same parent device. It's also not udev which fails on newer
> > installations, it's the lack of information in the non-extensible
> > deprecated layout which makes all sorts of tools fail. So please
> > work-off the text from the old help text instead of blaming the wrong
> > things here. :)
> 
> Ok. I can either send out a new patch or Greg can change the description
> of v2 to dish out the blame in a Kay approved matter when he merges it.
> What you guys prefer.

Heh, I've edited the wording a bit now.

thanks,

greg k-h

      parent reply	other threads:[~2010-09-21 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 14:54 Andi Kleen
2010-09-08 15:27 ` Kay Sievers
2010-09-08 17:39   ` Andi Kleen
2010-09-08 21:56     ` Greg KH
2010-09-21 20:26     ` Greg KH [this message]

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=20100921202621.GA25112@kroah.com \
    --to=greg@kroah.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=axboe@kernel.dk \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome