From: Greg KH <greg@kroah.com>
To: 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 19:31:04 -0700 [thread overview]
Message-ID: <20070330023104.GA21771@kroah.com> (raw)
In-Reply-To: <20070329004138.GA23562@nostromo.devel.redhat.com>
On Wed, Mar 28, 2007 at 08:41:38PM -0400, Bill Nottingham wrote:
> Greg KH (greg@kroah.com) said:
> > If you follow the rules in Documentation/ABI/testing/sysfs-class your
> > program will not have any problems.
>
> Oh, of *course*. We add interfaces and then claim years later,
> after code has been written, "Oh, you shouldn't be using that!" in
> documentation. Meanwhile, such code using the old interface will still
> a) continue to compile b) continue to run without any sort of warnings.
>
> 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:
commit c18f6365fdbaf30611a8822afcd7097865dcaa32
Author: Greg Kroah-Hartman <gregkh@suse.de>
Date: Thu Apr 27 14:10:12 2006 -0700
[PATCH] Add kernel<->userspace ABI stability documentation
And Kay and I have been saying to not to rely on directories for over
two years now...
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.
If you have any problems with that option enabled, please let me know
and I will be glad to fix it up.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-30 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 17:01 new sysfs layout and ethernet device names 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 [this message]
2007-03-30 3:29 ` Bill Nottingham
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=20070330023104.GA21771@kroah.com \
--to=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