From: Mark Brown <broonie@kernel.org>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: next-20151126 build: 3 failures 15 warnings (next-20151126)
Date: Thu, 26 Nov 2015 13:22:28 +0000 [thread overview]
Message-ID: <20151126132228.GG1929@sirena.org.uk> (raw)
In-Reply-To: <87y4dllysz.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
On Thu, Nov 26, 2015 at 02:39:40PM +0200, Kalle Valo wrote:
> Mark Brown <broonie@kernel.org> writes:
> > It looks like this was somehow triggered as part of the reorganisation
> > of the WiFi directory structure.
> This is surprising and also worrying, any ideas why? It would be good to
> understand the root cause in case there's a bug in wireless drivers
> directory reorganisation.
No, I didn't make much effort to check though since the use of ifdef was
clearly a bug waiting to happen anyway, I was more surprised it worked
at all than anything.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-11-26 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 9:06 next-20151126 build: 3 failures 15 warnings (next-20151126) Build bot for Mark Brown
2015-11-26 11:32 ` Mark Brown
2015-11-26 15:10 ` Catalin Marinas
2015-11-26 23:30 ` Daniel Cashman
2015-11-26 11:59 ` Mark Brown
2015-11-26 12:15 ` Mark Brown
[not found] ` <20151126121551.GE1929-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-11-26 12:39 ` Kalle Valo
2015-11-26 13:22 ` Mark Brown [this message]
2015-11-26 16:58 ` Kalle Valo
2015-11-26 17:03 ` Mark Brown
2015-11-26 18:34 ` Kalle Valo
[not found] ` <878u5kmwya.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2015-11-26 20:58 ` Mark Brown
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=20151126132228.GG1929@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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