From: Stephen Rothwell <sfr@canb.auug.org.au>
To: <linux-next@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: linux-next: Tree for Jan 23
Date: Wed, 23 Jan 2013 17:43:36 +1100 [thread overview]
Message-ID: <20130123174336.47c0113740a14da7f6a92187@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2680 bytes --]
Hi all,
Changes since 20130122:
The powerpc tree still had a build failure.
The wireless-next tree gained conflicts against the net and linus' trees.
The sound-asoc tree gained a build failure so I used the version from
next-20130122.
The trivial tree gained conflicts against the mips and pm trees.
The leds tree gained a build failure do I used the version from
next-20130122.
The driver-core tree gained a conflict against Linus' tree.
The staging tree gained a conflict against the net-next tree.
The gpio-lw tree lost its build failure.
The pinctrl tree gained a conflict against the driver-core tree.
The tegra tree gained conflicts against the arm-soc and pm trees.
----------------------------------------------------------------------------
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" 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,
sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 211 trees (counting Linus' and 28 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
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.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-01-23 6:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:43 Stephen Rothwell [this message]
2013-01-23 22:18 ` linux-next: Tree for Jan 23 Stephen Rothwell
2013-01-23 23:10 ` linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c]) Randy Dunlap
2013-01-23 23:23 ` Herbert Xu
2013-01-23 23:41 ` Randy Dunlap
2013-01-26 10:02 ` Jonathan Cameron
2013-01-23 23:28 ` linux-next: Tree for Jan 23 (pch_uart.c) Randy Dunlap
2013-01-24 2:06 ` Stephen Rothwell
2013-01-24 2:30 ` Liang Li
2013-01-24 4:15 ` Stephen Rothwell
2013-01-24 4:25 ` Liang Li
2013-01-23 23:56 ` linux-next: Tree for Jan 23 (hvc and virtio_console) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 2:29 linux-next: Tree for Jan 23 Stephen Rothwell
2023-01-23 4:31 Stephen Rothwell
2020-01-23 6:21 Stephen Rothwell
2019-01-23 5:24 Stephen Rothwell
2017-01-23 5:08 Stephen Rothwell
2015-01-23 7:10 Stephen Rothwell
2015-01-23 18:34 ` Guenter Roeck
2014-01-23 6:21 Stephen Rothwell
2014-01-23 6:38 ` Stephen Rothwell
2014-01-23 14:44 ` Paul Gortmaker
2012-01-23 3:11 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=20130123174336.47c0113740a14da7f6a92187@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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).