From: Bill Nottingham <notting@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>, linux-kernel@vger.kernel.org
Subject: Re: new sysfs layout and ethernet device names
Date: Thu, 29 Mar 2007 23:29:05 -0400 [thread overview]
Message-ID: <20070330032905.GA4384@nostromo.devel.redhat.com> (raw)
In-Reply-To: <20070330023104.GA21771@kroah.com>
Greg KH (greg@kroah.com) said:
> > If interfaces have to change, so be it. But changing the rules for
> > using them years after it's implemented and then claiming "you didn't
> > read the instructions" is pretty lame.
>
> That documentation has been in the kernel tree for almost a full year:
It has a date on it. I'm not blind. That doesn't change the fact that
that documentation:
> Date: Thu Apr 27 14:10:12 2006 -0700
postdates the interface it's describing by at *least* two years. Which
was the point of my mail that you conveniently ignored - retroactively
deciding which parts of the interface you export to userspace shouldn't be
used falls way short of best practices.
> Anyway, yes, older code should still "just work" if you enable the
> CONFIG_SYSFS_DEPRECATED config option in the kernel, that is what it is
> there for.
It appears to... the point was that (as far as the code is concerned)
it's a silent break. Of course, code that expects the 'current' layout
will then break when this new change is made, unless you add
CONFIG_SYSFS_SLIGHTLY_LESS_DEPRECATED?
Bill
next prev parent reply other threads:[~2007-03-30 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 17:01 Bill Nottingham
2007-03-22 8:47 ` Kay Sievers
2007-03-28 3:17 ` Bill Nottingham
2007-03-28 4:10 ` Greg KH
2007-03-29 0:41 ` Bill Nottingham
2007-03-30 2:31 ` Greg KH
2007-03-30 3:29 ` Bill Nottingham [this message]
2007-03-30 5:26 ` 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=20070330032905.GA4384@nostromo.devel.redhat.com \
--to=notting@redhat.com \
--cc=greg@kroah.com \
--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