From: Mark Brown <broonie@kernel•org>
To: linux-next@vger•kernel.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, linux-kernel@vger•kernel.org
Subject: linux-next: Tree for 3rd December
Date: Thu, 3 Dec 2015 23:31:43 +0000 [thread overview]
Message-ID: <20151203233143.GI5727@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2015-12-03 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 23:31 Mark Brown [this message]
2015-12-06 22:46 ` linux-next: Tree for 3rd December Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151203233143.GI5727@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox