From: Andrew Morton <akpm@linux-foundation.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, WANG Cong <amwang@redhat.com>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: 2.6.31 -mm merge plans
Date: Wed, 10 Jun 2009 12:16:33 -0700 [thread overview]
Message-ID: <20090610121633.d678fc8b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090610190841.GT8633@ZenIV.linux.org.uk>
(cc's added)
On Wed, 10 Jun 2009 20:08:41 +0100
Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Wed, Jun 10, 2009 at 11:51:40AM -0700, Andrew Morton wrote:
>
> > proc-merge-arrayc-into-basec.patch
> > proc-merge-arrayc-into-basec-checkpatch-fixes.patch
>
> I'm not sure that there's any point in that. Sure, we can slap two
> files together; what the hell for? Both are quite large, there's
> a (relatively) sane separation of code between them (misc. files
> contents in /proc/<pid>/ vs. directory structure and symlinks in
> there, more or less) and I don't see any benefit in mashing them
> together. Up to Alexey, but IMO that's pointless.
No strong opinions here.
AFAIK Alexey isn't doing procfs any more?
next prev parent reply other threads:[~2009-06-10 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 18:51 2.6.31 -mm merge plans Andrew Morton
2009-06-10 19:00 ` mac80211-use-kzfree-in-key-handling-to-enforce-data-sanitization (was Re: 2.6.31 -mm merge plans) John W. Linville
2009-06-10 19:08 ` 2.6.31 -mm merge plans Al Viro
2009-06-10 19:16 ` Andrew Morton [this message]
2009-06-11 1:15 ` Amerigo Wang
2009-06-11 3:10 ` Al Viro
2009-06-11 5:25 ` Amerigo Wang
2009-06-13 20:53 ` Eric W. Biederman
2009-06-11 2:23 ` KOSAKI Motohiro
2009-06-11 11:40 ` mmc_spi-use-eilseq-for-possible-transmission-errors.patch (was Re: 2.6.31 -mm merge plans) Matt Fleming
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=20090610121633.d678fc8b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=amwang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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