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, akpm@linux-foundation.org
Subject: linux-next: Tree for 2nd December
Date: Thu, 3 Dec 2015 01:18:14 +0000 [thread overview]
Message-ID: <20151203011814.GC5727@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Hi all,
Changes since 20151127:
The block and gpio trees gained build failures so I used the versions
from next-20151127.
There were quite a lot of new conflicts from Arnd's arm multiplatform
series which I fixed up, plus a few other new conflicts from other
sources.
I messed up using Stephen's scripts so only the akpm-current tree was
merged of Andrew Morton's trees. Sorry about that, it's gone 1am so I'm
not about to try to fix anything up.
I will run a build again tomorrow (Thursday 3rd). I *may* also do one
on Friday but it will have less build coverage and may not appear till
Saturday if I do.
Non-merge commits (relative to Linus' tree): 3399
5261 files changed, 719667 insertions(+), 620445 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 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 1:18 Mark Brown [this message]
2015-12-03 8:38 ` [PATCH] of: fix build failure Sudip Mukherjee
2015-12-05 11:09 ` Geert Uytterhoeven
2015-12-07 6:36 ` Sudip Mukherjee
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=20151203011814.GC5727@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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