Hi, I've finally gotten off my butt and made my quilt trees of patches into a "semi-proper" git tree to make it easier for people to test them. I'm now pushing the patches I accept into the stable queues into the git tree here: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git I'll push them out in chunks, as I accept them, and when I do a "real" -rc release. Right now the HEAD of each branch will have a -rc1 tag on them, just because it makes it a bit easier on my end. Note these branches WILL get rebased. All the time. So don't count on them to contain anything that will stick around, UNTIL a real stable release happens. Guenter, I hope this helps with your testing, is there anything that I can do here to make it easier for you? Kevin, hopefully this tree also helps you. I will also be adding some email headers to my announcements of the -rc releases that you can parse. Here is what they are going to look like for an example release: X-KernelTest-Patch: http://kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.14-rc1.gz X-KernelTest-Tree: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git X-KernelTest-Branch: linux-4.4.y X-KernelTest-Patches: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git X-KernelTest-Version: 4.4.14-rc1 X-KernelTest-Deadline: 2016-06-20T02:57+00:00 Will those work out? Fengguang, can you add these to the 0-day bot? The branches to watch are all of the currently-active stable trees. Right now that would be "linux-3.14.y", "linux-4.4.y", and "linux-4.6.y". Do I need to tell you about future branches, or can you just pick up new ones when they show up? And can I get announcements if/when the tests pass (or fail) so I know all is ok? Hope this helps people out, thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html