From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ulrich Drepper <drepper@redhat.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] CPU online file permission
Date: Tue, 31 Jul 2007 17:38:55 +1000 [thread overview]
Message-ID: <1185867535.6131.56.camel@localhost.localdomain> (raw)
In-Reply-To: <20070730165720.37780cc6.akpm@linux-foundation.org>
On Mon, 2007-07-30 at 16:57 -0700, Andrew Morton wrote:
> On Sun, 29 Jul 2007 20:56:46 -0400
> Ulrich Drepper <drepper@redhat.com> wrote:
>
> > Is there a reason why the "online" file in the subdirectories for the CPUs
> > in /sys/devices/system isn't world-readable?
>
> No sane one which I can think of. It seems that it originally sprang forth
> from Rusty's keyboard in that form.
Hmm, that seems possible but unlikely. My original version used proc,
after all.
But either way, fix is good.
Rusty.
prev parent reply other threads:[~2007-07-31 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 0:56 [PATCH] CPU online file permission Ulrich Drepper
2007-07-30 23:57 ` Andrew Morton
2007-07-31 7:38 ` Rusty Russell [this message]
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=1185867535.6131.56.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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