linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for Sep 20
Date: Fri, 20 Sep 2019 17:36:37 +0100	[thread overview]
Message-ID: <20190920163637.GI3822@sirena.co.uk> (raw)

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

Hi all,

News: There will likely be no more -next builds until Stephen returns on
the 30th, I *may* do some next week but it's more likely that I won't
and it certainly won't be every day.

Changes since 20190919:

The thermal tree gained a conflict with Linus' tree which I fixed up.

The akpm-current tree gained a conflict with the risc-v-fixes tree which
I fixed up.

Non-merge commits (relative to Linus' tree): 2719
 2712 files changed, 92075 insertions(+), 40381 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.

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 311 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
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  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-20 16:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 16:36 Mark Brown [this message]
2019-09-20 19:48 ` linux-next: Tree for Sep 20 (amd/display) Randy Dunlap
2019-09-20 22:35 ` linux-next: Tree for Sep 20 (amdgpu-2) Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2024-09-20  4:33 linux-next: Tree for Sep 20 Stephen Rothwell
2023-09-20  3:37 Stephen Rothwell
2022-09-20  8:15 Stephen Rothwell
2021-09-20  6:35 Stephen Rothwell
2018-09-20  5:12 Stephen Rothwell
2018-09-20 10:37 ` Michael Ellerman
2018-09-20 11:10   ` Stephen Rothwell
2018-09-20 11:17     ` Stephen Rothwell
2018-09-20 14:02       ` Rob Herring
2018-09-24  3:43         ` Michael Ellerman
2017-09-20  4:21 Stephen Rothwell
2016-09-20  8:04 Stephen Rothwell
2013-09-20  4:45 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=20190920163637.GI3822@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).