From: Russell King <rmk@arm.linux.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dawson Engler <engler@csl.Stanford.EDU>, linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 9 potential copy_*_user bugs in 2.4.1
Date: Fri, 16 Mar 2001 19:26:46 +0000 [thread overview]
Message-ID: <20010316192646.A8755@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200103160224.SAA03920@csl.Stanford.EDU> <1886.984737208@redhat.com>
In-Reply-To: <1886.984737208@redhat.com>; from dwmw2@infradead.org on Fri, Mar 16, 2001 at 10:06:48AM +0000
On Fri, Mar 16, 2001 at 10:06:48AM +0000, David Woodhouse wrote:
> Nice work - thanks. One request though, to you and anyone else doing such
> cleanups - please could you list the affected files separately near the
> beginning of your mail, so that people can tell at a glance whether there's
> anything in there that might be their fault.
Also, it'd be nice if the filenames were in alphabetic order. Both points
make it much easier to examine the list of affected files.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-16 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 2:24 [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Dawson Engler
2001-03-16 3:11 ` Alexander Viro
2001-03-16 7:36 ` Dawson Engler
2001-03-16 13:05 ` Jamie Lokier
2001-03-16 5:54 ` Greg KH
2001-03-16 7:07 ` David S. Miller
2001-03-16 10:06 ` David Woodhouse
2001-03-16 19:26 ` Russell King [this message]
2001-03-16 20:56 ` Locking question (was: [CHECKER] 9 potential copy_*_user bugs in 2.4.1) Nigel Gamble
2001-03-20 8:42 ` [CHECKER] 9 potential copy_*_user bugs in 2.4.1 Rusty Russell
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=20010316192646.A8755@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dwmw2@infradead.org \
--cc=engler@csl.Stanford.EDU \
--cc=linux-kernel@vger.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