From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: next-20160427 build: 1 failures 15 warnings (next-20160427)
Date: Wed, 27 Apr 2016 16:48:04 +0200 [thread overview]
Message-ID: <20160427144802.GA4176@ulmo.ba.sec> (raw)
In-Reply-To: <20160427122438.GK3217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Wed, Apr 27, 2016 at 01:24:38PM +0100, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Apr 27, 2016 at 10:50:51AM +0100, Build bot for Mark Brown wrote:
>
> Today's next fails to build an arm64 allmodconfig due to:
>
> > arm64-allmodconfig
> > ../drivers/phy/tegra/xusb-tegra210.c:1721:3: error: label 'out' used but not defined
>
> caused by 44f5d38eaa21d (phy: tegra: Add Tegra210 support).
Yes, I just realized this now as well. I pushed a fix to Tegra's
for-next, so this should be fixed in tomorrow's linux-next.
Sorry for this.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-04-27 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 9:50 next-20160427 build: 1 failures 15 warnings (next-20160427) Build bot for Mark Brown
2016-04-27 12:24 ` Mark Brown
[not found] ` <20160427122438.GK3217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-04-27 14:48 ` Thierry Reding [this message]
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=20160427144802.GA4176@ulmo.ba.sec \
--to=treding-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=kishon-l0cyMroinI0@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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