From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Set CONFIG_SYSFS_DEPRECATED_V2=n
Date: Tue, 14 Sep 2010 08:37:12 +0000 [thread overview]
Message-ID: <20100914083712.GN7336@linux-sh.org> (raw)
In-Reply-To: <2bf9c3bb585d142503d6b7f3669e2138ba9ed112.1282398356.git.matt@console-pimps.org>
On Sun, Aug 22, 2010 at 07:06:01PM +0900, Paul Mundt wrote:
> On Sat, Aug 21, 2010 at 03:13:44PM +0100, Matt Fleming wrote:
> > On Sat, Aug 21, 2010 at 02:47:59PM +0100, Matt Fleming wrote:
> > > As the help for the config option suggests, this option really shouldn't
> > > be set by default for any recent distribution as it changes the layout
> > > of sysfs. I spotted this while running debian when udev got very
> > > confused by the sysfs layout and failed to create some device nodes.
> > >
> > > Signed-off-by: Matt Fleming <matt@console-pimps.org>
> > > ---
> > > arch/sh/configs/sh7785lcr_defconfig | 1 -
> > > 1 files changed, 0 insertions(+), 1 deletions(-)
> >
> > Hmm.. on second thought, this option should probably be removed from all
> > the defconfigs in arch/sh/configs as it defaults to 'n' in
> > init/Kconfig. Unless anyone knows of a specific reason to leave it
> > enabled for a particular board?
>
> No, the only reason it is still enabled for some boards is because people
> rarely if ever send defconfigs updates that actually match the configs
> being regularly used. Killing it off uniformly is fine.
Ok, I actually forgot to apply this, so it's applied now. Hopefully that
will be the end of that!
prev parent reply other threads:[~2010-09-14 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 13:47 [PATCH] sh: Set CONFIG_SYSFS_DEPRECATED_V2=n Matt Fleming
2010-08-21 14:13 ` Matt Fleming
2010-08-21 14:49 ` Matt Fleming
2010-08-22 10:06 ` Paul Mundt
2010-09-14 8:37 ` Paul Mundt [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=20100914083712.GN7336@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).