From: Guenter Roeck <linux@roeck-us.net>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Oct 9
Date: Wed, 9 Oct 2013 10:55:35 -0700 [thread overview]
Message-ID: <20131009175535.GA8847@roeck-us.net> (raw)
In-Reply-To: <20131009154424.GA8564@roeck-us.net>
On Wed, Oct 09, 2013 at 08:44:24AM -0700, Guenter Roeck wrote:
> On Wed, Oct 09, 2013 at 08:29:06AM -0700, Guenter Roeck wrote:
> > On Wed, Oct 09, 2013 at 04:14:22PM +0200, Thierry Reding wrote:
> > > Hi all,
> > >
> > > I've uploaded today's linux-next tree to the master branch of the
> > > repository below:
> > >
> > > git://gitorious.org/thierryreding/linux-next.git
> > >
> > > A next-20131009 tag is also provided for convenience.
> > >
> > > Gained a few conflicts, but nothing too exciting. x86, ARM, PowerPC and
> > > MIPS default configurations build fine. There were some build failures
> > > unrelated to the merge, most of which I fixed and added as patches on
> > > top of the final merge.
> > >
> > Build results:
> > total: 110 pass: 93 skipped: 4 fail: 13
> > [3.12-rc4: total: 110 pass: 105 skipped: 3 fail: 2]
> >
> > Failed builds:
> > alpha:allmodconfig
> > arm:allmodconfig
> > blackfin:defconfig
> > i386:allyesconfig
> > i386:allmodconfig
> > m68k:allmodconfig
> > mips:allmodconfig
> > mips:nlm_xlp_defconfig
> > powerpc:allmodconfig
> > sparc64:allmodconfig
> > x86_64:allmodconfig
> > x86_64:allyesconfig
> > xtensa:allmodconfig
> >
> > Many of the failures are due to ceph:
> >
> > fs/ceph/file.c: In function 'ceph_sync_read':
> > fs/ceph/file.c:437:25: error: 'struct iov_iter' has no member named 'iov'
> > ...
> >
> Sorry, that was the result for yesterday's tree. I should have results for the
> October 9 tree in a couple of hours.
>
October 9 results are exactly the same.
Guenter
next prev parent reply other threads:[~2013-10-09 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 14:14 linux-next: Tree for Oct 9 Thierry Reding
2013-10-09 14:14 ` [PATCH] ipv6: Unbreak build Thierry Reding
2013-10-09 14:41 ` Eric Dumazet
2013-10-10 10:48 ` Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the clk tree Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the drm-intel tree Thierry Reding
2013-10-09 14:14 ` linux-next: manual merge of the imx-mxs tree Thierry Reding
2013-10-09 16:56 ` Fabio Estevam
2013-10-09 14:14 ` linux-next: manual merge of the mvebu tree Thierry Reding
2013-10-09 14:21 ` Jason Cooper
2013-10-09 14:37 ` Jason Cooper
2013-10-10 10:57 ` Thierry Reding
2013-10-10 11:40 ` Jason Cooper
2013-10-09 15:29 ` linux-next: Tree for Oct 9 Guenter Roeck
2013-10-09 15:44 ` Guenter Roeck
2013-10-09 17:55 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-09 5:17 Stephen Rothwell
2020-10-09 9:14 Stephen Rothwell
2019-10-09 5:09 Stephen Rothwell
2018-10-09 8:02 Stephen Rothwell
2018-10-10 0:50 ` Guenter Roeck
2015-10-09 6:24 Stephen Rothwell
2014-10-09 7:11 Stephen Rothwell
2012-10-09 3:43 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=20131009175535.GA8847@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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).