archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <>
To: Linux Next Mailing List <>
Cc: Linux Kernel Mailing List <>
Subject: linux-next: Tree for Sep 18
Date: Wed, 18 Sep 2019 23:10:53 +0100	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

Hi all,

Changes since 20190917:

The sound-current tree gained a build failure for which I reverted a

The driver-core tree gained a merge failure which I fixed up.

Non-merge commits (relative to Linus' tree): 8551
 7914 files changed, 621805 insertions(+), 224850 deletions(-)


I have created today's linux-next tree at
(patches at ).  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

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, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf.

Below is a summary of the state of the merge.

I am currently merging 310 trees (counting Linus' and 77 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at .

Status of my local build tests will be at .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-09-18 22:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 22:10 Mark Brown [this message]
2019-09-19  4:04 ` linux-next: Tree for Sep 18 (objtool) Randy Dunlap
2019-09-19 16:51   ` Josh Poimboeuf
2019-09-19 19:21     ` Randy Dunlap
2019-09-19 19:40       ` Josh Poimboeuf
2019-09-19 21:09         ` Randy Dunlap
2019-09-23  9:20   ` Peter Zijlstra
2019-09-23 12:49     ` Josh Poimboeuf
2019-09-23 13:33       ` Peter Zijlstra
2019-09-23 14:16         ` Josh Poimboeuf
2019-09-23 14:28           ` Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2020-09-18  8:44 linux-next: Tree for Sep 18 Stephen Rothwell
2018-09-18  5:12 Stephen Rothwell
2017-09-18  2:19 Stephen Rothwell
2015-09-18  4:08 Stephen Rothwell
2014-09-18  6:53 Stephen Rothwell
2013-09-18  5:07 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).