From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: please include init-v4.1-rc6 branch for v4.2
Date: Wed, 3 Jun 2015 17:41:15 -0400 [thread overview]
Message-ID: <20150603214114.GP29898@windriver.com> (raw)
In-Reply-To: <20150603185452.GV14071@sirena.org.uk>
[Re: [linux-next] please include init-v4.1-rc6 branch for v4.2] On 03/06/2015 (Wed 19:54) Mark Brown wrote:
> On Wed, Jun 03, 2015 at 01:39:04PM +1000, Stephen Rothwell wrote:
> > On Tue, 2 Jun 2015 19:23:18 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
>
> > > Please include init-v4.1-rc6 branch of:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git
>
> > OK, I will add it in just before I merge Andrew's tree and see how it
> > goes.
>
> It looks like this has broken every build that includes modules which
> I'm trying in my build reports - lots of implicit declarations breaking
> the build.
The module build fails [on ARM] seem worse than they are since the one
interaction with the tegra/fuse driver causes spew to appear from
generic files like device.h
https://lkml.kernel.org/r/20150603160808.GM29898@windriver.com
Thanks for the build coverage during the A/C outage; I'll follow up to
your build report with more details shortly; indicating exatly what has
been done to fix what.
Paul.
next prev parent reply other threads:[~2015-06-03 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 23:23 [linux-next] please include init-v4.1-rc6 branch for v4.2 Paul Gortmaker
2015-06-03 3:39 ` Stephen Rothwell
2015-06-03 18:54 ` [linux-next] " Mark Brown
2015-06-03 21:41 ` Paul Gortmaker [this message]
2015-07-15 20:59 ` Paul Gortmaker
2015-07-16 0:06 ` [linux-next] " 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=20150603214114.GP29898@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=broonie@kernel.org \
--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).