From: Arnd Bergmann <arnd@arndb.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cleanup of compat_ioctl functions
Date: Wed, 8 Oct 2003 22:26:15 +0200 [thread overview]
Message-ID: <200310082226.15104.arnd@arndb.de> (raw)
In-Reply-To: <20031008192929.GC1035@elf.ucw.cz>
On Wednesday 08 October 2003 21:29, Pavel Machek wrote:
> Also __u32 should not be used here, it looks too ugly and u32 is
> okay. Same for __u16 and __u64. Its simple search&replace, and as you
> are doing lots of changes, anyway....
Well, in the light of 'strictly bug fixes only', it was probably too
much search&replace already. I guess I'll have to prepare a new patch
that just fixes the bugs in the current s390 compat_ioctl code and not
use fs/compat_ioctl.c in 2.6.0.
Arnd <><
next prev parent reply other threads:[~2003-10-08 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 16:09 [PATCH] cleanup of compat_ioctl functions Arnd Bergmann
2003-10-08 19:29 ` Pavel Machek
2003-10-08 20:26 ` Arnd Bergmann [this message]
2003-10-08 21:02 ` David S. Miller
2003-10-08 21:35 ` Pavel Machek
2003-10-08 22:49 ` Arnd Bergmann
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=200310082226.15104.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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