From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: Mark Brown <broonie@kernel.org>, Christoph Hellwig <hch@lst.de>,
Darren Hart <dvhart@linux.intel.com>,
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
"David S. Miller" <davem@davemloft.net>,
huangdaode <huangdaode@hisilicon.com>,
linux-next@vger.kernel.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next-20151015 build: 3 failures 46 warnings (next-20151015)
Date: Thu, 15 Oct 2015 15:29:34 +0200 [thread overview]
Message-ID: <6421942.GNUzHZNjcs@wuerfel> (raw)
In-Reply-To: <20151015115933.GD14956@sirena.org.uk>
On Thursday 15 October 2015 12:59:33 Mark Brown wrote:
> On Thu, Oct 15, 2015 at 12:31:22PM +0100, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build both arm and arm64 allmodconfig with:
>
> > arm64-allmodconfig
> > ../drivers/net/ethernet/hisilicon/hns/hns_dsaf_xgmac.c:10:47: fatal error: asm-generic/io-64-nonatomic-hi-lo.h: No such file or directory
>
> > arm-allmodconfig
> > ../drivers/net/ethernet/hisilicon/hns/hns_dsaf_xgmac.c:10:47: fatal error: asm-generic/io-64-nonatomic-hi-lo.h: No such file or directory
>
> This was triggered by f626fe17485b6dc (move io-64-nonatomic*.h out of
> asm-generic) which moved these helpers out of asm-generic (which should
> never be directly referenced outside of arch code anyway so arches can
> provide their own implementations as needed) and into linux/. Since the
> HiSilicon driver has been added in -next it wasn't updated as part of
> the same commit.
>
I've added a workaround in my asm-generic branch now, by adding back
a header in the old place that we can remove in 4.5 after we change over
this one and another one in mtd that Stephen has caught in linux-next.
Arnd
prev parent reply other threads:[~2015-10-15 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 11:31 next-20151015 build: 3 failures 46 warnings (next-20151015) Build bot for Mark Brown
2015-10-15 11:59 ` Mark Brown
2015-10-15 13:29 ` Arnd Bergmann [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=6421942.GNUzHZNjcs@wuerfel \
--to=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=dvhart@linux.intel.com \
--cc=hch@lst.de \
--cc=huangdaode@hisilicon.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=mitake.hitoshi@lab.ntt.co.jp \
/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