From: viro@parcelfarce.linux.theplanet.co.uk
To: Christoph Hellwig <hch@lst.de>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove unused funcion proc_mknod
Date: Mon, 5 May 2003 20:22:48 +0100 [thread overview]
Message-ID: <20030505192248.GD10374@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030505190045.A22238@lst.de>
On Mon, May 05, 2003 at 07:00:45PM +0200, Christoph Hellwig wrote:
> Not used currently and a rather bad idea in general..
That is true, but note that ALAS^H^HSA creates device nodes in /proc
manually. IOW, removal of proc_mknod() won't solve anything. The
real question is whether we should allow device nodes on procfs.
If we should not allow them, ALSA needs API changes. If we should,
it'd be better to have creation of such nodes explicit (and if ALSA
keeps doing that, it should switch to calling proc_mknod()).
next prev parent reply other threads:[~2003-05-05 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 17:00 [PATCH] remove unused funcion proc_mknod Christoph Hellwig
2003-05-05 19:22 ` viro [this message]
2003-05-05 19:30 ` Christoph Hellwig
2003-05-05 20:45 ` Jeff Garzik
2003-05-09 11:43 ` Jaroslav Kysela
2003-05-09 11:47 ` Christoph Hellwig
2003-05-09 11:55 ` Jaroslav Kysela
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=20030505192248.GD10374@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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