LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for May 24
Date: Fri, 25 May 2018 18:30:25 +0100	[thread overview]
Message-ID: <20180525173025.GO4828@sirena.org.uk> (raw)

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

Hi all,

This tree is being released on the 25th but it's actually a snapshot
from the 24th that I started building on the 24th but didn't go as
quickly as hoped, sorry.  There should be another linux-next done by me
for today (25th) as well, that will appear tomorrow all being well.

Stephen should be back on Monday.

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 277 trees (counting Linus' and 64 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 .

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

             reply	other threads:[~2018-05-25 17:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 17:30 Mark Brown [this message]
2018-05-27 18:46 ` Mark Brown
2018-05-27 19:20   ` Stephen Rothwell
2018-05-28  9:08   ` Arnd Bergmann
2018-05-28 11:04     ` Mark Brown
2018-05-28 12:23 ` Andy Shevchenko
2018-05-29 10:38   ` Mark Brown
2018-05-29 11:18     ` Stephen Rothwell
2018-05-29 11:37       ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2022-05-24  9:26 Stephen Rothwell
2021-05-24  6:08 Stephen Rothwell
2019-05-24  4:07 Stephen Rothwell
2017-05-24  3:23 Stephen Rothwell
2016-05-24  2:43 Stephen Rothwell
2012-05-24  6:49 Stephen Rothwell
2011-05-24  4:02 Stephen Rothwell
2010-05-24  3:57 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=20180525173025.GO4828@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for May 24' \
    /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

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).