On Mon, May 14, 2018 at 10:20 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi all, > > Changes since 20180511: > > New trees: btrfs-fixes > vfs-fixes > dma-mapping-fixes > > The f2fs tree gained a conflict against the vfs-fixes tree. > > The bpf-next tree gained a conflict against the bpf tree. > > The rcu tree gained a conflict against Linus' tree. > > The kselftest tree gained a conflict against the kvm-fixes tree. > > Non-merge commits (relative to Linus' tree): 5724 > 5580 files changed, 217262 insertions(+), 101414 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 > are tracking the linux-next tree using git, you should not use "git pull" > to do so as that will try to merge the new linux-next release with the > old one. You should use "git fetch" and checkout or reset to the new > master. Hmm... It seems my message was buried in the pile of the thread WRT fixes branches. Please, add our PDx86 fixes branch as well: git://git.infradead.org/linux-platform-drivers-x86.git fixes -- With Best Regards, Andy Shevchenko -- 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
