From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Weinehall <tao@acc.umu.se>
Cc: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Todo] Remove usage of (f)suser in kernel
Date: Wed, 05 Dec 2001 13:14:16 -0500 [thread overview]
Message-ID: <3C0E63F8.8CD0B9CA@mandrakesoft.com> (raw)
In-Reply-To: <20011205181558.R360@khan.acc.umu.se>
David Weinehall wrote:
> After a quick round of grep:ing, I came up with the following files
> needing fixes to substitute usage of (f)suser for proper capabilities:
[...]
> Since I don't know what the maintainers of some of these files want
> as capabilities, I've decided not to fix this myself. zr36120.c is
> only a matter of removing an #ifdef/#else/#endif combo and doing some
> reindenting, though.
We need to kill those in 2.5 I think. s/suser/capable(...)/ has been on
the kernel janitor's list for a while.
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-12-05 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 17:15 [Todo] Remove usage of (f)suser in kernel David Weinehall
2001-12-05 18:14 ` Jeff Garzik [this message]
2001-12-05 18:35 ` David Weinehall
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=3C0E63F8.8CD0B9CA@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
/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