From: Christoph Hellwig <hch@infradead.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: ebiederm@xmission.com, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, containers@lists.osdl.org,
sds@tycho.nsa.gov, jmorris@namei.org
Subject: Re: [PATCH 1/6] proc: implement support for automounts in task directories
Date: Tue, 6 Jan 2009 04:21:14 -0500 [thread overview]
Message-ID: <20090106092114.GA11877@infradead.org> (raw)
In-Reply-To: <20090105233241.GA3924@x200.localdomain>
On Tue, Jan 06, 2009 at 02:32:41AM +0300, Alexey Dobriyan wrote:
> This is current version of /proc/net as separate file system patchset,
> rebased, etc. I'll put it into -next again when merge window closes.
I still don't see the point for that. Why not /proc/nets/<netid> with
symlinks from /proc/<pid>/net into those?
next prev parent reply other threads:[~2009-01-06 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 23:32 [PATCH 1/6] proc: implement support for automounts in task directories Alexey Dobriyan
2009-01-05 23:36 ` Alexey Dobriyan
2009-01-06 9:21 ` Christoph Hellwig [this message]
2009-01-06 12:20 ` Eric W. Biederman
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=20090106092114.GA11877@infradead.org \
--to=hch@infradead.org \
--cc=adobriyan@gmail.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=viro@zeniv.linux.org.uk \
/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