From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] ABI feature gates?
Date: Fri, 4 Aug 2017 13:27:04 +1000 [thread overview]
Message-ID: <20170804132704.73c49b64@canb.auug.org.au> (raw)
In-Reply-To: <20170804022639.p27oliuinqqatar2@thunk.org>
Hi Ted,
On Thu, 3 Aug 2017 22:26:39 -0400 Theodore Ts'o <tytso@mit.edu> 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. Unfortunately there will be a lot of false negatives, so
> it's going to require a human to figure out which of the changes
> represent new/changed API's, and which are just cleanups /
> rearragements. (We could try to see if we could train a Machine
> Learning model --- but even if we can make a some nueral nets play Go,
> I'm personally dubious this is something that ML would be successful
> at. I might be pleasantly surprised, though, if someone wanted to
> give it a try. :-)
OK, so this is what we have so far in linux-next:
$ git log --no-merges --pretty="%h %s" stable..next-20170803 include/uapi
9aa302aaede8 membarrier: Expedited private command
b3a88f222ae1 drm/msm: Add a parameter query for the number of ringbuffers
7f1779fd071b drm/msm: Implement per-submitqueue fences
20ab08455d3c drm/msm: Add per-instance submit queues
80fe969b5d50 uapi: fix linux/sysctl.h userspace compilation errors
4edc19eeeee3 mm: userfaultfd: add feature to request for a signal delivery
0d33bdf5ea6c mm: shm: use new hugetlb size encoding definitions
b217edddf5c2 mm: arch: consolidate mmap hugetlb size encodings
21d75dd8e83d mm: hugetlb: define system call hugetlb size encodings in single file
cdbc78ba7026 drm/msm: Remove __user from __u64 data types
db1689aa61bd drm: Create a format/modifier blob
e6fc3b68558e drm: Plumb modifiers through plane init
bb7c19f96012 tcp: add related fields into SCM_TIMESTAMPING_OPT_STATS
3282e65558b3 tcp: remove unused mib counters
615095752100 netfilter: nf_tables: Allow object names of up to 255 chars
387454901bd6 netfilter: nf_tables: Allow set names of up to 255 chars
b7263e071aba netfilter: nf_tables: Allow chain name of up to 255 chars
e46abbcc05aa netfilter: nf_tables: Allow table names of up to 255 chars
e62e484df049 net sched actions: add time filter for action dumping
90825b23a887 net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch
64c83d837329 net netlink: Add new type NLA_BITFIELD32
1a5f3da20bd9 net: ethtool: add support for forward error correction modes
ca1136c99b66 blktrace: export cgroup info in trace
f30994622b2b drm/vc4: Add an ioctl for labeling GEM BOs for summary stats
67cbe3532c2c RDMA/qedr: notify user application of supported WIDs
ad84dad2160d RDMA/qedr: notify user application if DPM is supported
cc731525f26a signal: Remove kernel interal si_code magic
d08477aa975e fcntl: Don't use ambiguous SIG_POLL si_codes
3078f5f1bd8b IB/mlx4: Add support for RSS QP
b8d46ca03506 IB/mlx4: Add support for WQ indirection table related verbs
400b1ebcfe31 IB/mlx4: Add support for WQ related verbs
ea30b966f7dd IB/mlx4: Add inline-receive support
2dee0e545894 IB/uverbs: Enable QP creation with a given source QP number
784b4e612d42 netfilter: nf_tables: Attach process info to NFT_MSG_NEWGEN notifications
ddc6c70f07bb rxrpc: Move the packet.h include file into net/rxrpc/
727f8914477e rxrpc: Expose UAPI definitions to userspace
eb0baf8a0d92 perf/core: Define the common branch type classification
6b2bbb08747a media: cec: rework the cec event handling
6303d97873d3 media: linux/cec.h: add pin monitoring API support
fc60a8b675bd tty: serial: owl: Implement console driver
97f91a7cf04f bpf: add bpf_redirect_map helper routine
546ac1ffb70d bpf: add devmap, a map for storing net device references
814abfabef3c xdp: add bpf_redirect helper function
66bf97967726 annotate RWF_... flags
6545135a5ed2 drm/qxl: fix __user annotations
Some of these are just fixing bugs or moving things around. I wonder
where we can go from here? Does every change to a uapi file need a
corresponding documentation and man pages update? Do we dare try doing
(shock! horror!) design before implementation? ;-)
The, of course, there is the whole sysfs and tracing mess :-(
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-08-04 3:27 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 [this message]
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
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=20170804132704.73c49b64@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@kernel.org \
--cc=tytso@mit.edu \
/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