Change the oss.oracle.com/git/tmem.git to git://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.git
Hey Stephen,
I am taking the role of maintaining the cleancache and working on making the frontswap patches acceptable for the upstream tree.
As this is merge window season, I've made the #linux-next branch be empty, but once the v3.3-rc1 branch is tagged I will start cracking on the patches.
CC-ing Dan here so he can add his SOB to this.
Please substitute the git://oss.oracle.com/djm/tmem.git tree with git://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.git
The branch to pull from is called #linux-next.
Thanks!
Quoted 14 lines
From: Konrad Rzeszutek Wilk
Sent: Thursday, January 12, 2012 12:16 PM
To: [email protected]; [email protected]; [email protected]; Dan Magenheimer
Subject: Change the oss.oracle.com/git/tmem.git togit://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.gitHey Stephen,
I am taking the role of maintaining the cleancache and working on making the frontswap patches acceptable for the upstream tree.
As this is merge window season, I've made the #linux-next branch be empty, but once the v3.3-rc1 branch is tagged I will start cracking on the patches.
Quoted 8 lines
CC-ing Dan here so he can add his SOB to this.
Please substitute the
git://oss.oracle.com/djm/tmem.gittree withgit://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.gitThe branch to pull from is called #linux-next.
Thanks!
Confirmed.
Dan
Hi Guys,
Quoted 9 lines · On Thu, 12 Jan 2012 11:20:07 -0800 (PST) Dan Magenheimer…
Quoted 9 lines
From: Konrad Rzeszutek Wilk
I am taking the role of maintaining the cleancache and working on making the frontswap patches acceptable for the upstream tree.
As this is merge window season, I've made the #linux-next branch be empty, but once the v3.3-rc1 branch is tagged I will start cracking on the patches.
Quoted 8 lines
Quoted 6 lines
CC-ing Dan here so he can add his SOB to this.
Please substitute the
git://oss.oracle.com/djm/tmem.gittree withgit://git.kernel.org/pub/scm/linux/kernel/git/konrad/mm.gitThe branch to pull from is called #linux-next.
Confirmed.
OK, I have switched to that today.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
Signature · 15 lines
Cheers, Stephen Rothwell [email protected] Legal Stuff: By participating in linux-next, your subsystem tree contributions are public and will be included in the linux-next trees. You may be sent e-mail messages indicating errors or other issues when the patches/commits from your subsystem tree are merged and tested in linux-next. These messages may also be cross-posted to the linux-next mailing list, the linux-kernel mailing list, etc. The linux-next tree project and IBM (my employer) make no warranties regarding the linux-next project, the testing procedures, the results, the e-mails, etc. If you don't agree to these ground rules, let me know and I'll remove your tree from participation in linux-next.