From: hollis@austin.ibm.com
To: Leigh Brown <leigh@solinno.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org, Sven Dickert <Sven.Dickert@planb.de>
Subject: Re: /proc/residual (CONFIG_PREP_PROCRESIDUAL)
Date: Tue, 29 Jan 2002 10:56:14 -0600 [thread overview]
Message-ID: <20020129165614.GV510@austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201291556160.3031-100000@fridge.solinno.co.uk>
On Tue, Jan 29, 2002 at 04:08:43PM +0000, Leigh Brown wrote:
>
> It works for me. The comment needs to be changed to say it can't be a
> module. I've attached the version I came up with, mainly because I went
> to some trouble to do it. Differences:
>
> 2. Remove #ifdef __KERNEL__ from header file for use space utility
This encourages user applications to include kernel header files, which has
been deemed ungood. I believe there should be many lengthy threads on the
subject in the lkml archives, but more practically speaking Paul has said he'd
be perfectly happy if all kernel headers were completely protected from user
space.
> 4. Only create entry if residual size > 0 'coz what you can't see won't
> hurt you + eliminate chance of people wondering why they are getting an
> error trying to read it.
I don't like that, because it leaves you wondering if you compiled in residual
support at all... I'd much rather have it be 0 length.
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-29 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 16:08 /proc/residual (CONFIG_PREP_PROCRESIDUAL) Tom Rini
2002-01-29 16:08 ` Leigh Brown
2002-01-29 16:56 ` hollis [this message]
2002-01-29 21:47 ` Leigh Brown
2002-01-29 22:03 ` Tom Rini
2002-01-30 20:47 ` Leigh Brown
2002-01-30 20:41 ` Tom Rini
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=20020129165614.GV510@austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=Sven.Dickert@planb.de \
--cc=leigh@solinno.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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).