hi, On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > Please do not add any v4.8 destined material to your linux-next included > branches until after v4.7-rc1 has been released. > > Changes since 20160516: > > The vfs tree gained a conflict against the ext4 tree. > > The net-next tree gained a conflict against the arm64 tree. > > The spi tree lost its build failure. > > Non-merge commits (relative to Linus' tree): 9737 > 8314 files changed, 424907 insertions(+), 177068 deletions(-) > > ---------------------------------------------------------------------------- > > I have created today's linux-next tree at > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you Patches after 0516 are not there. i'm chasing an oom issue between 0516 and 0518 trees while missed 0517 tag, so is the patch file the only way to get there trying 0517 tree? -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
