On Thu, Nov 09, 2017 at 02:35:37PM +0100, Arnd Bergmann wrote: > On Thu, Nov 9, 2017 at 1:48 PM, Greg KH <greg@xxxxxxxxx> wrote: > > On Thu, Nov 09, 2017 at 12:40:36PM +0000, Ben Hutchings wrote: > >> On Thu, 2017-11-09 at 13:21 +0100, Arnd Bergmann wrote: > >> > On Thu, Nov 9, 2017 at 1:08 PM, Greg KH <greg@xxxxxxxxx> wrote: > >> > > On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote: > >> [...] > >> > > > I think if you upload the branch to the stable-rc git, that should produce > >> > > > the automated build and boot results via email or via the > >> > > > https://kernelci.org/job/ interface. Once there are some results > >> > > > there, I'll go through the list once more to see what warnings > >> > > > and failures remain. > >> > > > >> > > I don't know of a way to have others push to that tree/branch at the > >> > > moment :( > >> > > > >> > > I'll go update that branch now... > >> > > >> > Thanks! > >> > > >> > With the arm-soc tree, we simply have a shared group-id on > >> > gitolite.kernel.org and everyone in that group can push to it. > >> > > >> > If that is the only thing you need, it should be trivial to let Ben > >> > and Sasha push to /pub/scm/linux/kernel/git/stable/*.git as well, > >> > I'm sure helpdesk@xxxxxxxxxx can arrange that. Of course if you are > >> > worried about having multiple accounts with write access to all the > >> > branches, then that wouldn't be enough. > >> > >> I think I'd rather send a pull request to Greg at the start of the > >> review period. > > > > That works for me! > > We just discussed this on the #kernelci IRC channel. Since kernelci > has a whitelist of branches and 3.16 isn't currently on it, how about > just adding a different git tree for Ben's 3.2-rc and 3.16-rc releases? > > Ben, do you have a git URL that we can add to kernelci, and and > an email address you want to see the build results at? > Would be great. Maybe I can then finally shut down kerneltests.org as redundant. Guenter