From: Jeremiah Mahler <jmmahler@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 4
Date: Thu, 4 Dec 2014 15:34:11 -0800 [thread overview]
Message-ID: <20141204233411.GA1223@hudson.localdomain> (raw)
In-Reply-To: <20141204195928.4a5b93f4@canb.auug.org.au>
all,
On Thu, Dec 04, 2014 at 07:59:28PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20141203:
>
> The usb tree still had its build failure so I used the version from
> next-20141128.
>
> Non-merge commits (relative to Linus' tree): 10075
> 9350 files changed, 375991 insertions(+), 275936 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 ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
> multi_v7_defconfig for arm. After the final fixups (if any), it is also
> built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
> allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
> defconfig.
>
> Below is a summary of the state of the merge.
>
> I am currently merging 229 trees (counting Linus' and 32 trees of patches
> pending for Linus' tree).
>
> 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.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
[...]
linux-next 20141204 is broken on all my machines, 20141203 worked fine.
They fail very early in the boot process and are unable to mount root.
There are lots of "ext4_check_descriptors: Checksum for group ...
failed" messages.
Any suggestions for where to start looking?
--
- Jeremiah Mahler
next prev parent reply other threads:[~2014-12-04 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 8:59 linux-next: Tree for Dec 4 Stephen Rothwell
2014-12-04 23:34 ` Jeremiah Mahler [this message]
2014-12-05 0:54 ` Jeremiah Mahler
2014-12-05 8:29 ` Dmitry Monakhov
-- strict thread matches above, loose matches on Subject: below --
2023-12-04 4:57 Stephen Rothwell
2020-12-04 10:20 Stephen Rothwell
2019-12-04 5:06 Stephen Rothwell
2018-12-04 6:46 Stephen Rothwell
2017-12-04 4:06 Stephen Rothwell
2013-12-04 3:01 Stephen Rothwell
2012-12-04 6:22 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=20141204233411.GA1223@hudson.localdomain \
--to=jmmahler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).