Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1283455

linux-next: Tree for 3rd December

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject linux-next: Tree for 3rd December
Date 2015-12-04 00:40 +0100
Message-ID <qBLDI-3fK-3@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi all,

Changes since 20151202:

Both of Andrew's trees are included.

The block and gpio trees still have their build failures so I used the
versions from next-20151127.

There were several new conflicts between the drm-intel-fixes and
drm-next trees.

It is very unlikely that there will be a build tomorrow, Stephen will be
back and -next will be back to normal on Monday.

Non-merge commits (relative to Linus' tree): 3709
 5435 files changed, 721155 insertions(+), 627700 deletions(-)

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
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.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a defconfig for arm64 and an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf.

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

linux-next: Tree for 3rd December Mark Brown <broonie@kernel.org> - 2015-12-04 00:40 +0100
  Re: linux-next: Tree for 3rd December Stephen Rothwell <sfr@canb.auug.org.au> - 2015-12-06 23:50 +0100

csiph-web