public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Cc: linux-kernel@vger•kernel.org
Subject: cleancache into linux-next, target for 2.6.37 merge window?
Date: Tue, 28 Sep 2010 12:31:18 -0700 (PDT)	[thread overview]
Message-ID: <40229210-a2a6-41ab-9a88-bde956ebc66c@default> (raw)

Hi --

The "cleancache" patchset crosses multiple subsystem boundaries and
at the recent filesystem/storage/mm summit, people suggested that
after the patchset has stabilized, I should just submit it to
linux-next and then directly to Linus.  The latest version has received
no further suggestions or comments.  Previous versions received
a great deal of review and comment from a wide variety of maintainers
across all the impacted subsystems, as documented in the commit logs.

Would it be possible to include the following tree in the linux-next
build process?

git://git.kernel.org/pub/scm/linux/kernel/git/djm/tmem.git#linux-next

The patchset applies cleanly against both 2.6.36-rc3 and -rc5.
Against next-20100928, I see two very minor merge conflicts in
mm/Kconfig and include/linux/fs.h due to minor changes from other
trees.

Thanks,
Dan Magenheimer
dan.magenheimer@oracle•com

             reply	other threads:[~2010-09-28 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 19:31 Dan Magenheimer [this message]
2010-09-29  0:48 ` cleancache into linux-next, target for 2.6.37 merge window? Stephen Rothwell

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=40229210-a2a6-41ab-9a88-bde956ebc66c@default \
    --to=dan.magenheimer@oracle$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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