archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <>
Cc: LKML <>,
	Linus <>
Subject: linux-next: Tree for Oct 25
Date: Tue, 25 Oct 2011 20:36:28 +1100	[thread overview]
Message-ID: <> (raw)

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

Hi all,

*Note well*

This tree has nate had any build testing at all.  As such, it probably
doesn't build :-) This tree is really just a roll up of the current state
of the trees when the v3.2 merge window opened.  It will not be put into
the build system referred to below.

The linux-next tree remains available from
git:// .  But this will probably be
the laste one available there.

It is also back on  The patch is still absent, however.

This tree is certainly broken on sparc :-(

Changes since 20111014:

Dropped tree: ptrace (at the maintainers request)

The arm-soc tree gained conflicts against the arm tree.

The at91 tree lost its conflict.

The s5p tree lost its conflicts.

The libata tree gained a conflict against the at91 tree.

The scsi tree gained a conflict against the s390 tree.

The bluetooth tree lost several conflicts but gained another agains
Linus' tree.

The security tree probably lost its build failure.

The pm tree gained a conflict against the s390 tree.

The tip tree gained conflicts against the cputime tree.

The driver-core tree gained a conflict against the net-next tree.

The tty tree gained conflicts against Linus' tree.

The staging tree gained a conflict against the net-next tree.

The moduleh tree gained conflicts agains the xen-two and Linus' tree.

The akpm tree gained conflicts against the driver-core and block trees
and I dropped a few patches that had turned up elsewhere.


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" as mentioned in the FAQ on the wiki
(see below).

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 ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc
and sparc64 defconfig. These builds also have
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 199 trees (counting Linus' and 27 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

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.

There is a wiki covering stuff to do with linux-next at .  Thanks to Frank Seidel.

Stephen Rothwell          

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

             reply	other threads:[~2011-10-25  9:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  9:36 Stephen Rothwell [this message]
2011-10-25  9:43 ` linux-next: Tree for Oct 25 Stephen Rothwell
2011-10-25 10:42 ` Stephen Rothwell
2011-10-26  0:34 ` linux-next: Tree for Oct 25 (agp/intel-gtt.c) Randy Dunlap
2011-11-03 21:21   ` Randy Dunlap
2011-10-26  0:42 ` linux-next: Tree for Oct 25 (crypto) Randy Dunlap
2011-10-26  6:27   ` Herbert Xu
2011-10-26 12:33     ` Stefan Richter
2011-10-26 16:27       ` Randy Dunlap
2011-10-26 17:15         ` Stefan Richter
2011-10-27  7:05     ` Valdis.Kletnieks
2011-10-27  7:45       ` Herbert Xu
2011-10-29 23:20         ` Valdis.Kletnieks
2011-10-26 18:26 ` linux-next: Tree for Oct 25 (mfd/ab8500) Randy Dunlap
2011-10-30 23:04   ` Samuel Ortiz
2011-10-26 18:37 ` linux-next: Tree for Oct 25 (pci/ats.c) Randy Dunlap
2011-11-10 13:09   ` Ingo Molnar
2011-10-26 18:39 ` linux-next: Tree for Oct 25 (target) Randy Dunlap
2011-10-26 19:53   ` Nicholas A. Bellinger
2011-10-26 20:40     ` Stephen Rothwell
2011-10-26 20:42       ` Nicholas A. Bellinger
2011-10-26 18:47 ` linux-next: Tree for Oct 25 (sb_edac.c) Randy Dunlap
2012-10-25  4:01 linux-next: Tree for Oct 25 Stephen Rothwell
2013-10-25 15:03 Thierry Reding
2013-10-25 21:01 ` Guenter Roeck
2013-10-25 22:31 ` Randy Dunlap
2013-10-26 16:59   ` Mark Brown
2013-10-28  8:01   ` Thierry Reding
2013-10-28 16:53     ` Mark Brown
2016-10-25  3:31 Stephen Rothwell
2016-10-26  1:09 ` Paul Gortmaker
2016-10-27  6:21   ` Daniel Vetter
2019-10-25  5:45 Stephen Rothwell
2021-10-25  9:49 Stephen Rothwell
2021-10-25 22:11 ` Dmitry Osipenko
2021-10-26  1:28   ` Ming Lei
2021-10-26  8:40     ` Dmitry Osipenko
2021-10-27 11:42 ` Stephen Rothwell
2021-10-27 12:54   ` Greg Kroah-Hartman
2021-10-28  1:51   ` Xianting Tian
2021-10-28  4:51     ` Stephen Rothwell
2021-10-28  7:59       ` Xianting Tian
2021-10-28 12:48         ` Stephen Rothwell
2021-10-28 12:54           ` Xianting Tian
2022-10-25  4:20 Stephen Rothwell
2023-10-25  5:37 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).