From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Alexander Viro <viro@math.psu.edu>
Cc: "David S. Miller" <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BKPATCH] X25: use seq_file for proc stuff
Date: Mon, 7 Oct 2002 01:03:05 -0300 [thread overview]
Message-ID: <20021007040305.GE1201@conectiva.com.br> (raw)
In-Reply-To: <Pine.GSO.4.21.0210062351380.29030-100000@weyl.math.psu.edu>
Em Sun, Oct 06, 2002 at 11:56:20PM -0400, Alexander Viro escreveu:
> Huh???
>
> a) ->permission() always returning 0 on a read-only file is... interesting.
> b) if you want it world-readable, kernel is perfectly capable of doing that;
> had been since the very beginning. Just set mode to 0444 and be done with
> that; no need to have anything special in ->proc_iops.
Just that? Cool, I'll be sending a fix in some minutes.
Thanks Al.
- Arnaldo
prev parent reply other threads:[~2002-10-07 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 3:31 [BKPATCH] X25: use seq_file for proc stuff Arnaldo Carvalho de Melo
2002-10-07 3:56 ` Alexander Viro
2002-10-07 4:03 ` Arnaldo Carvalho de Melo [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=20021007040305.GE1201@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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