From: Al Viro <viro@ftp.linux.org.uk>
To: Jeff Bailey <jbailey@raspberryginger.com>
Cc: David Miller <davem@davemloft.net>,
tgraf@suug.ch, drow@false.org, stefan@loplof.de,
dwmw2@infradead.org, joseph@codesourcery.com,
netdev@vger.kernel.org, libc-alpha@sourceware.org, akpm@osdl.org
Subject: Re: [NETLINK]: Schedule removal of old macros exported to userspace
Date: Sun, 10 Dec 2006 01:52:27 +0000 [thread overview]
Message-ID: <20061210015227.GZ4587@ftp.linux.org.uk> (raw)
In-Reply-To: <5b2e36650612091742u70188d90l25e91c33468a0c0a@mail.gmail.com>
On Sat, Dec 09, 2006 at 08:42:45PM -0500, Jeff Bailey wrote:
> On 09/12/06, David Miller <davem@davemloft.net> wrote:
> >You can't deprecate stuff visible to userspace, sorry Thomas,
> >we just can't do it.
> >
> >You can migrate people to "better" interfaces, but you can't
> >pull the rug out from anyone once things like this are visible
> >to userspace. It's permanently there, and we have to live with
> >that.
>
> Is there some way of marking it so that newer architectures that come
> on don't wind up with that export? That way at least as newer
> machines and arches come out, they don't have to carry the oldest
> baggage. As the oldest architectures eventually get dropped, cruft
> can be removed.
Which architectures ever got dropped?
next prev parent reply other threads:[~2006-12-10 1:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 17:20 Kernel header changes break glibc build Joseph S. Myers
2006-12-03 12:25 ` David Woodhouse
2006-12-04 9:13 ` Thomas Graf
2006-12-06 13:01 ` David Woodhouse
2006-12-06 13:43 ` Jakub Jelinek
2006-12-06 13:51 ` David Woodhouse
2006-12-06 13:57 ` Jakub Jelinek
2006-12-06 14:01 ` David Woodhouse
2006-12-06 13:59 ` Thomas Graf
2006-12-06 14:07 ` David Woodhouse
2006-12-06 14:18 ` Jakub Jelinek
2006-12-06 14:31 ` Thomas Graf
2006-12-06 17:13 ` Al Viro
2006-12-06 20:26 ` Thomas Graf
2006-12-06 20:34 ` Al Viro
2006-12-06 21:35 ` Thomas Graf
2006-12-06 14:23 ` Thomas Graf
2006-12-07 11:29 ` David Woodhouse
2006-12-06 19:32 ` Stefan Rompf
2006-12-06 20:22 ` Thomas Graf
2006-12-07 0:56 ` David Miller
2006-12-07 10:47 ` Thomas Graf
2006-12-07 10:51 ` David Miller
2006-12-07 10:55 ` [NETLINK]: Restore API compatibility of address and neighbour bits Thomas Graf
2006-12-07 11:28 ` David Woodhouse
2006-12-08 7:52 ` David Miller
2006-12-08 7:50 ` David Miller
2006-12-08 14:25 ` Stefan Rompf
2006-12-08 17:33 ` Jim Gifford
2006-12-08 17:54 ` Mike Frysinger
2006-12-08 21:33 ` David Miller
2006-12-08 21:36 ` Daniel Jacobowitz
2006-12-08 21:47 ` David Miller
2006-12-08 21:52 ` Daniel Jacobowitz
2006-12-09 0:43 ` David Miller
2006-12-09 1:14 ` David Miller
2006-12-09 10:39 ` [NETLINK]: Schedule removal of old macros exported to userspace Thomas Graf
2006-12-09 11:49 ` Stefan Rompf
2006-12-09 12:55 ` Thomas Graf
2006-12-09 14:58 ` Stefan Rompf
2006-12-09 21:50 ` David Miller
2006-12-09 22:02 ` David Woodhouse
2006-12-12 11:23 ` David Woodhouse
2006-12-09 21:49 ` David Miller
2006-12-09 21:45 ` David Miller
2006-12-09 23:28 ` Thomas Graf
2006-12-10 10:11 ` Stefan Rompf
2006-12-10 12:15 ` Thomas Graf
2006-12-12 6:56 ` dhcpclient netlink bugs (was Re: [NETLINK]: Schedule removal of old macros exported to userspace) Stefan Rompf
2006-12-15 0:46 ` Herbert Xu
2006-12-10 1:42 ` [NETLINK]: Schedule removal of old macros exported to userspace Jeff Bailey
2006-12-10 1:52 ` Al Viro [this message]
2006-12-09 9:56 ` [NETLINK]: Restore API compatibility of address and neighbour bits Stefan Rompf
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=20061210015227.GZ4587@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=drow@false.org \
--cc=dwmw2@infradead.org \
--cc=jbailey@raspberryginger.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@loplof.de \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.