From: Greg KH <greg@kroah.com>
To: Hannes Reinecke <hare@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] ABI feature gates?
Date: Fri, 4 Aug 2017 09:04:54 -0700 [thread overview]
Message-ID: <20170804160454.GC13098@kroah.com> (raw)
In-Reply-To: <c2091a67-0a06-44ae-86e0-84879f3c7865@suse.com>
On Fri, Aug 04, 2017 at 10:53:01AM +0200, Hannes Reinecke wrote:
> On 08/04/2017 10:42 AM, Jiri Kosina wrote:
> > On Thu, 3 Aug 2017, Theodore Ts'o wrote:
> >
> >> One way that we could try to make things better is by having some kind
> >> of semi-automated system which monitors changes in include/uapi/*.h in
> >> linux-next.
> >
> > It's unfortunately just uapi though, and for sysfs it's a bit more
> > difficult to define a pathname pattern to watch for.
> >
> Yeah; that has been my main headache with the kABI stuff.
> Nowadays sysfs is considered part of the kABI, but we have no way of
> tracking it; we basically rely on people filling out some off-side
> documentation, and hope they're not missing anything.
> And we don't mess up when generating patches :-)
We could start searching linux-next for new additions of sysfs files
(search for the ATTR macros), and complain that there are no matching
Documentation/ABI/ updates at the same time. I try to do that when
reviewing patches that come through my trees, but yes, this is hard to
keep up to date with.
Sounds like a good GSoC project though, setting up the infrastructure to
do this in a semi-automated fashion.
greg k-h
next prev parent reply other threads:[~2017-08-04 16:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 1:16 Andy Lutomirski
2017-08-04 1:30 ` Greg KH
2017-08-04 4:15 ` Andy Lutomirski
2017-08-04 5:08 ` Sergey Senozhatsky
2017-08-04 8:23 ` Daniel Vetter
2017-08-04 2:26 ` Theodore Ts'o
2017-08-04 3:27 ` Stephen Rothwell
2017-08-04 5:13 ` Julia Lawall
2017-08-04 14:20 ` Theodore Ts'o
2017-08-04 15:47 ` Julia Lawall
2017-08-04 8:42 ` Jiri Kosina
2017-08-04 8:53 ` Hannes Reinecke
2017-08-04 16:04 ` Greg KH [this message]
2017-08-04 17:14 ` Theodore Ts'o
2017-08-04 17:53 ` Greg KH
2017-08-04 22:52 ` Joe Perches
2017-08-09 20:06 ` Geert Uytterhoeven
2017-08-14 19:49 ` Steven Rostedt
2017-08-14 19:51 ` Linus Torvalds
2017-08-15 7:13 ` Julia Lawall
2017-08-04 8:57 ` Julia Lawall
2017-08-04 11:27 ` Michael Kerrisk (man-pages)
2017-08-09 0:00 ` NeilBrown
2017-08-09 11:54 ` Laurent Pinchart
2017-08-14 20:07 ` Steven Rostedt
2017-08-09 20:21 ` Linus Torvalds
2017-08-11 6:21 ` NeilBrown
2017-08-11 6:39 ` Linus Torvalds
2017-08-11 8:02 ` NeilBrown
2017-08-11 23:10 ` Linus Torvalds
2017-08-14 4:19 ` NeilBrown
2017-08-14 18:34 ` Linus Torvalds
2017-08-14 18:40 ` Linus Torvalds
2017-08-14 23:23 ` Andy Lutomirski
2017-08-15 0:54 ` Linus Torvalds
2017-08-15 16:11 ` Andy Lutomirski
2017-08-15 18:26 ` Michael Kerrisk (man-pages)
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=20170804160454.GC13098@kroah.com \
--to=greg@kroah.com \
--cc=hare@suse.com \
--cc=ksummit-discuss@lists.linuxfoundation.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