From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Greg KH <greg@kroah.com>
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 14:08:36 +0900 [thread overview]
Message-ID: <20170804050836.GB6084@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170804013010.GA425@kroah.com>
On (08/03/17 18:30), Greg KH wrote:
[..]
> > There's a few problems here. One is that the people who would really
> > review the ABI might not even notice until step 5 or 6 or so. Another
> > is that it takes some time for userspace to get experience with a new
> > ABI.
> >
> > I'm wondering if there are other models that could work. I think it
> > would be nice for us to be able to land a kernel in Linus tree and
> > still wait a while before stabilizing it. Rust, for example, has a
> > strict policy for this that seems to work quite well.
>
> What does Rust do here?
I think Andy meant how Rust tags all of its features:
...
#[stable(feature = "rust1", since = "1.0.0")]
fn finish(&self) -> u64;
/// Writes some data into this `Hasher`.
///
/// # Examples
///
/// ```
/// use std::collections::hash_map::DefaultHasher;
/// use std::hash::Hasher;
///
/// let mut hasher = DefaultHasher::new();
/// let data = [0x01, 0x23, 0x45, 0x67, 0x89, 0xab, 0xcd, 0xef];
///
/// hasher.write(&data);
///
/// println!("Hash is {:x}!", hasher.finish());
/// ```
#[stable(feature = "rust1", since = "1.0.0")]
fn write(&mut self, bytes: &[u8]);
/// Writes a single `u8` into this hasher.
#[inline]
#[stable(feature = "hasher_write", since = "1.3.0")]
fn write_u8(&mut self, i: u8) {
self.write(&[i])
}
/// Writes a single `u16` into this hasher.
#[inline]
#[stable(feature = "hasher_write", since = "1.3.0")]
fn write_u16(&mut self, i: u16) {
self.write(&unsafe { mem::transmute::<_, [u8; 2]>(i) })
}
#[unstable(feature = "sip_hash_13", issue = "34767")]
#[allow(deprecated)]
pub use self::sip::{SipHasher13, SipHasher24};
...
-ss
next prev parent reply other threads:[~2017-08-04 5:08 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 [this message]
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
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=20170804050836.GB6084@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@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