From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesper Juhl <juhl-lkml@dif.dk>,
yuasa@hh.iij4u.or.jp, linux-kernel@vger.kernel.org
Subject: Re: [patch][resend] convert a remaining verify_area to access_ok (was: Re: [PATCH 2.6.11-mm1] mips: more convert verify_area to access_ok) (fwd)
Date: Thu, 17 Mar 2005 13:14:55 +0000 [thread overview]
Message-ID: <20050317131455.GB5204@linux-mips.org> (raw)
In-Reply-To: <20050316145524.18787569.akpm@osdl.org>
On Wed, Mar 16, 2005 at 02:55:24PM -0800, Andrew Morton wrote:
> Jesper Juhl <juhl-lkml@dif.dk> wrote:
> >
> > Around 2.6.11-mm1 Yoichi Yuasa found a user of verify_area that I had
> > missed when converting everything to access_ok. The patch below still
> > applies cleanly to 2.6.11-mm4.
> > Please apply (unless of course you already picked it up back then and
> > have it in a queue somewhere :) .
>
> That's tricky stuff you're playing with, so I'd prefer it came in via Ralf.
> However I can queue it up locally so it doesn't get forgotten.
>
> Ralf must have another two megabyte patch buffered up by now, btw?
Quite a bit less and much of the diff are patches that must be somewhere
in Jeff's network driver queue. But yes, hint taken, you'll get your
patch easter egg ;-0
Ralf
next prev parent reply other threads:[~2005-03-17 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 21:35 [patch][resend] convert a remaining verify_area to access_ok (was: Re: [PATCH 2.6.11-mm1] mips: more convert verify_area to access_ok) (fwd) Jesper Juhl
2005-03-16 22:55 ` Andrew Morton
2005-03-16 23:01 ` Jesper Juhl
2005-03-17 13:14 ` Ralf Baechle [this message]
2005-03-17 21:44 ` Ralf Baechle
2005-03-17 21:43 ` Ralf Baechle
2005-03-18 0:17 ` Jesper Juhl
2005-03-18 22:56 ` Ralf Baechle
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=20050317131455.GB5204@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@osdl.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=yuasa@hh.iij4u.or.jp \
/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.