From: Andi Kleen <ak@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Linus Torvalds" <torvalds@osdl.org>,
"Jesper Juhl" <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, alan@redhat.com,
"Russell King" <rmk+lkml@arm.linux.org.uk>,
"Jakub Jelinek" <jakub@redhat.com>,
"Mike Galbraith" <efault@gmx.de>,
"Albert Cahalan" <acahalan@gmail.com>,
"Bill Nottingham" <notting@redhat.com>,
"Marco Roeland" <marco.roeland@xs4all.nl>,
"Michael Kerrisk" <mtk-manpages@gmx.net>
Subject: Re: [PATCH] sysctl: Undeprecate sys_sysctl (take 2)
Date: Fri, 10 Nov 2006 07:50:10 +0100 [thread overview]
Message-ID: <200611100750.10990.ak@suse.de> (raw)
In-Reply-To: <m1ejsd3e38.fsf_-_@ebiederm.dsl.xmission.com>
On Wednesday 08 November 2006 20:58, Eric W. Biederman wrote:
>
> The basic issue is that despite have been ``deprecated'' and
> warned about as a very bad thing in the man pages since it's
> inception there are a few real users of sys_sysctl.
But they only seem to use a small number of actually used with
sysctl(2) sysctls.
I still think just maintaining a conversion table for
those is the right thing to do.
The important part really is to get rid of the crufty
old infrastructure internally.
-Andi
next prev parent reply other threads:[~2006-11-10 6:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 19:00 [PATCH] sysctl: Undeprecate sys_sysctl Eric W. Biederman
2006-11-08 19:10 ` Jesper Juhl
2006-11-08 19:58 ` [PATCH] sysctl: Undeprecate sys_sysctl (take 2) Eric W. Biederman
2006-11-10 6:50 ` Andi Kleen [this message]
2006-11-10 7:28 ` Eric W. Biederman
2006-11-11 5:27 ` H. Peter Anvin
2006-11-08 20:49 ` [PATCH] sysctl: Undeprecate sys_sysctl Alan Cox
2006-11-08 20:55 ` Arjan van de Ven
2006-11-09 17:27 ` H. Peter Anvin
2006-11-09 23:17 ` Alistair John Strachan
2006-11-10 5:21 ` Eric W. Biederman
2006-11-10 7:56 ` Russell King
2006-11-10 8:13 ` Eric W. Biederman
2006-11-11 8:04 ` Russell King
2006-11-10 8:50 ` Alistair John Strachan
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=200611100750.10990.ak@suse.de \
--to=ak@suse.de \
--cc=acahalan@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=ebiederm@xmission.com \
--cc=efault@gmx.de \
--cc=jakub@redhat.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
--cc=mtk-manpages@gmx.net \
--cc=notting@redhat.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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 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.