archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <>
Subject: linux-next: Tree for Sep 2
Date: Tue, 2 Sep 2014 19:36:17 +0100	[thread overview]
Message-ID: <> (raw)

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

Changes since 20140901:

The akpm-current tree lost its conflict against Linus' tree and two
patches from it got applied.

Non-merge commits (relative to Linus' tree): 3078
 2790 files changed, 105584 insertions(+), 81173 deletions(-)

I have created today's linux-next tree at
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 an
allmodconfig for x86_64 and a multi_v7_defconfig for arm.

Below is a summary of the state of the merge.

I am currently merging 214 trees (counting Linus' and 30 trees of patches
pending for Linus' tree).

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

Status of Stephen's 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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-09-02 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 18:36 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-02  6:23 linux-next: Tree for Sep 2 Stephen Rothwell
2020-09-02  8:09 Stephen Rothwell
2019-09-02 12:43 Stephen Rothwell
2015-09-02  8:17 Stephen Rothwell
2014-09-03 19:01 Mark Brown
2013-09-02  9:21 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).