From: David Mosberger <davidm@napali.hpl.hp.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: torvalds@transmeta.com,
kernel list <linux-kernel@vger.kernel.org>,
alan@redhat.com
Subject: Re: sys32_ioctl: kill code duplication
Date: Tue, 18 Mar 2003 14:36:52 -0800 [thread overview]
Message-ID: <15991.40836.398583.695871@napali.hpl.hp.com> (raw)
In-Reply-To: <20030315221214.GA2102@elf.ucw.cz>
Pavel> Hi!
Pavel> This kills code duplication in sys32_ioctl. It should work on x86-64
Pavel> and sparc64; other architecture maintainers said that "anything that
Pavel> moves code out of arch/*/kernel/ioctl32.c is welcome" or similar.
Pavel> Linus, what is required to make it go in?
Pavel> Alan, would you be willing to let this be merged through you?
I think it's a good idea to get rid of the ioctl code duplication, but
since the code involved is often subtle, I think it should be tested
on all affected architectures first (or, at least, there should be
some argument as to why the new code is no worse than the old one).
In the particular case of ia64, I'd suggest to ask on
linux-ia64@linuxia64.org for a volunteer to test the patch.
--daivd
prev parent reply other threads:[~2003-03-18 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 22:12 Pavel Machek
2003-03-18 22:36 ` David Mosberger [this message]
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=15991.40836.398583.695871@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=alan@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®