From: Jesper Juhl <juhl-lkml@dif.dk>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: [PATCH][0/4] let's kill verify_area
Date: Fri, 7 Jan 2005 02:18:11 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.61.0501070212560.3430@dragon.hygekrogen.localhost> (raw)
verify_area() if just a wrapper for access_ok() (or similar function or
dummy function) for all arch's. I say it's time we just get rid of it as
it no longer serves any purpose and it's easy to convert to access_ok.
Converting all users may take some time, so initially deprecate it (which
will get the janitors attention as well as maintainers and ordinary users)
and then when all users of the function are converted we can kill it and
all comments related to it.
The following patches deprecate the function for all arch's and then do a
few initial conversions just to get things moving.
Comments are welcome.
--
Jesper Juhl
next reply other threads:[~2005-01-07 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 1:18 Jesper Juhl [this message]
2005-01-07 1:26 ` [PATCH][0/4] let's kill verify_area Andrew Morton
2005-01-07 1:49 ` Jesper Juhl
2005-01-07 1:56 ` Andrew Morton
2005-01-09 1:20 ` Jesper Juhl
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=Pine.LNX.4.61.0501070212560.3430@dragon.hygekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=akpm@osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).