From: Thierry Reding <thierry.reding@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"J. German Rivera" <German.Rivera@freescale.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org
Subject: Re: next-20160217 build: 3 failures 14 warnings (next-20160217)
Date: Thu, 18 Feb 2016 14:59:45 +0100 [thread overview]
Message-ID: <20160218135945.GB3941@ulmo.nvidia.com> (raw)
In-Reply-To: <20160218134326.GD7129@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Thu, Feb 18, 2016 at 01:43:26PM +0000, Mark Brown wrote:
> On Thu, Feb 18, 2016 at 11:31:42AM +1100, Stephen Rothwell wrote:
> > On Wed, 17 Feb 2016 11:22:25 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> > > The fsl-mc code is still breaking the build in -next, can we please drop
> > > the code or mark the driver as built in only until the MSI symbol
> > > exports are available? This is making it difficult to spot other
> > > errors.
>
> > I will add a merge fixup patch for the staging tree that makes
> > CONFIG_FSL_MC_BUS depend on CONFIG_BROKEN. Sorry, I should have done
> > this when it first came to light.
>
> Thanks! It'd still be good to get an actual fix in there though...
I'll ping Greg on the two patches that I sent on Monday.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-18 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:28 next-20160217 build: 3 failures 14 warnings (next-20160217) Build bot for Mark Brown
2016-02-17 11:22 ` Mark Brown
2016-02-18 0:31 ` Stephen Rothwell
2016-02-18 13:43 ` Mark Brown
2016-02-18 13:59 ` Thierry Reding [this message]
2016-02-19 22:48 ` Greg Kroah-Hartman
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=20160218135945.GB3941@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=German.Rivera@freescale.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.