From: Mark Brown <broonie@kernel•org>
To: Daniel Vetter <daniel@ffwll•ch>
Cc: Xinliang Liu <xinliang.liu@linaro•org>,
Xinwei Kong <kong.kongxinwei@hisilicon•com>,
Archit Taneja <architt@codeaurora•org>,
Sean Paul <seanpaul@chromium•org>,
Daniel Vetter <daniel.vetter@intel•com>,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
dri-devel@lists•freedesktop.org,
kernel-build-reports@lists•linaro.org
Subject: Re: next-20160817 build: 2 failures 5 warnings (next-20160817)
Date: Wed, 17 Aug 2016 11:45:35 +0100 [thread overview]
Message-ID: <20160817104535.GI9347@sirena.org.uk> (raw)
In-Reply-To: <20160817101453.GT6232@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Wed, Aug 17, 2016 at 12:14:53PM +0200, Daniel Vetter wrote:
> On Wed, Aug 17, 2016 at 10:26:44AM +0100, Mark Brown wrote:
> > caused by d25bcfb8c2 (drm/hisilicon: Don't set drm_device->platformdev)
> > which does a a partial conversion to new APIs.
> Yeah I screwed up since I naively assumed that compile testing on arm
> 32bit multiarch is good enough. I'm setting up an arm64 environment now,
> but would be nice if arm folks would stop loving bazillions of configs so
> much ;-)
There's only two you really need to care about for this sort of thing,
arm allmodconfig and arm64 allmodconfig (the equivalent of i386 and
x86-64) - there are some things that don't fit into either but they're
all legacy systems, those in active use are pretty much covered by those
two.
It's also worth adding || COMPILE_TEST dependencies onto architecture
lists to improve coverage if they don't have any actual architecture
dependency (which is the norm these days, at least for ARM), the
dependencies are useful for normal users so they're not asked about
drivers which clearly they can't use.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-08-17 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 7:28 next-20160817 build: 2 failures 5 warnings (next-20160817) Build bot for Mark Brown
2016-08-17 9:26 ` Mark Brown
2016-08-17 10:14 ` Daniel Vetter
2016-08-17 10:45 ` Mark Brown [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=20160817104535.GI9347@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=architt@codeaurora$(echo .)org \
--cc=daniel.vetter@intel$(echo .)com \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=kong.kongxinwei@hisilicon$(echo .)com \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=seanpaul@chromium$(echo .)org \
--cc=xinliang.liu@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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