public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Greg KH <greg@kroah.com>, Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	axboe@kernel.dk, tiwai@suse.de,
	James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH] SYSFS: Allow boot time switching between deprecated and modern sysfs layout II
Date: Wed, 8 Sep 2010 16:11:41 +0200	[thread overview]
Message-ID: <20100908161141.194e6785@basil.nowhere.org> (raw)
In-Reply-To: <20100908160235.61ae1200@basil.nowhere.org>

On Wed, 8 Sep 2010 16:02:35 +0200
Andi Kleen <andi@firstfloor.org> wrote:

> On Wed, 8 Sep 2010 06:55:30 -0700
> Greg KH <greg@kroah.com> wrote:
> 
> > But, Kay and I just changed the logic in the kernel in this area,
> > getting rid of the CONFIG_SYSFS_DEPRECATED_V2 option entirely, to
> > try to make the code path smaller, only offering the "old" mode for
> > block devices, to keep kernels booting on userspace instances like
> > what you have.
> 
> That will likely break my user space, it relies on the old style
> net set up (opensuse 10.0) for network configuration. 
> That was the main reason I did this patch.

... Just tested it. Never mind, it looks the old style network
configuration seems to work still with this patch and my 
earlier pessimistic assumptions were incorrect.

Don't see any misfunction so it looks like the new patch
is ok.

I'll respin my patch on top of this.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2010-09-08 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 13:19 [PATCH] SYSFS: Allow boot time switching between deprecated and modern sysfs layout Andi Kleen
2010-09-08 13:55 ` Greg KH
2010-09-08 14:02   ` Andi Kleen
2010-09-08 14:11     ` Andi Kleen [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=20100908161141.194e6785@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ak@linux.intel.com \
    --cc=axboe@kernel.dk \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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