linux-kernel - cleancache into linux-next, target for 2.6.37 merge window?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <40229210-a2a6-41ab-9a88-bde956ebc66c@default>
Date:	Tue, 28 Sep 2010 12:31:18 -0700 (PDT)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: cleancache into linux-next, target for 2.6.37 merge window?

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@...cle.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/