From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Al Viro <viro@ZenIV.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: clearcache (Was: Re: [git pull] vfs pile 1)
Date: Thu, 13 Jan 2011 21:42:39 +1100 [thread overview]
Message-ID: <20110113214239.1b23b523.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110113085547.GA7414@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Hi Christoph,
On Thu, 13 Jan 2011 03:55:47 -0500 Christoph Hellwig <hch@infradead.org> wrote:
>
> How did cleancache end up in linux-next again?
Um, I asked after the last merge window (on November 17, cc'ing you, Al
and Linus) and the only reply I got was from Dan saying that he was
hoping to work more on it with some chance of being ready for 2.6.38 ...
So, let me ask again:
"I didn't really follow the discussion at Kernel Summit, but there seemed
to be some question as to whether the cleancache stuff will be merged or
not. It missed 2.6.37 (obviously), but my question now is do I keep in
in linux-next in the hope that it will be merged in 2.6.38? Or is that
not going to happen?"
(The cleancache tree has not changed since October 9 last year.)
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-01-13 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 5:35 [git pull] vfs pile 1 Al Viro
2011-01-13 6:25 ` Stephen Rothwell
2011-01-13 8:55 ` Christoph Hellwig
[not found] ` <20110113214239.1b23b523.sfr@canb.auug.org.au20110113220039.GF31800@thunk.org>
2011-01-13 10:42 ` Stephen Rothwell [this message]
2011-01-13 16:08 ` clearcache (Was: Re: [git pull] vfs pile 1) Dan Magenheimer
2011-01-13 22:00 ` Ted Ts'o
2011-01-14 21:11 ` Dan Magenheimer
2011-01-14 22:35 ` Ted Ts'o
2011-01-14 23:28 ` Dan Magenheimer
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=20110113214239.1b23b523.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dan.magenheimer@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).