From: Dan Magenheimer <dan.magenheimer@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linus <torvalds@linux-foundation•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Al Viro <viro@ZenIV•linux.org.uk>, Christoph Hellwig <hch@lst•de>,
Andrew Morton <akpm@linux-foundation•org>
Subject: RE: linux-next: fate of the cleancache tree
Date: Tue, 16 Nov 2010 20:44:42 -0800 (PST) [thread overview]
Message-ID: <e5499ef1-c26d-4c9c-9336-5c61e65e45bc@default> (raw)
In-Reply-To: <20101117133324.0654bfd9.sfr@canb.auug.org.au>
> From: Stephen Rothwell [mailto:sfr@canb•auug.org.au]
> To: Linus; Dan Magenheimer
> Cc: linux-next@vger•kernel.org; linux-kernel@vger•kernel.org; Al Viro;
> Christoph Hellwig; Andrew Morton
> Subject: linux-next: fate of the cleancache tree
>
> Hi Linus, Dan,
>
> 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?
Hi Stephen --
I am continuing to work towards other users for cleancache. While
it is not clear if they will be ready in time for the 2.6.38 window,
it is possible. If it is not too difficult to keep cleancache in
linux-next for now, I'd appreciate it if it stayed in. However
if you or Linus prefer otherwise, I understand.
Thanks,
Dan
prev parent reply other threads:[~2010-11-17 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 2:33 linux-next: fate of the cleancache tree Stephen Rothwell
2010-11-17 4:44 ` Dan Magenheimer [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=e5499ef1-c26d-4c9c-9336-5c61e65e45bc@default \
--to=dan.magenheimer@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=hch@lst$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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