From: David Miller <davem@davemloft.net>
To: sre@kernel.org
Cc: broonie@kernel.org, kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: next-20170608 build: 1 failures 4 warnings (next-20170608)
Date: Thu, 08 Jun 2017 10:17:57 -0400 (EDT) [thread overview]
Message-ID: <20170608.101757.1257358800507365931.davem@davemloft.net> (raw)
In-Reply-To: <20170608113326.zo3nqwkbx3k42owz@earth>
From: Sebastian Reichel <sre@kernel.org>
Date: Thu, 8 Jun 2017 13:33:26 +0200
> Hi,
>
> On Thu, Jun 08, 2017 at 11:32:31AM +0100, Mark Brown wrote:
>> On Thu, Jun 08, 2017 at 10:57:50AM +0100, Build bot for Mark Brown wrote:
>>
>> Today's -next fails to build an ARM allmodconfig due to:
>>
>> > arm-allmodconfig
>> > ../drivers/hsi/clients/ssi_protocol.c:1069:5: error: 'struct net_device' has no member named 'destructor'
>>
>> due to cf124db566e6 (net: Fix inconsistent teardown and release of
>> private netdev state.) which missed this instance, presumably due to a
>> combination of it not being in one of the normal networking driver
>> directories and only being buildable on ARM.
>
> I assume, that this will be fixed via the net tree.
> If you Cc me on updated/new patch I will provide Acked-by.
It is fixed in the 'net' tree, don't worry about it :-)
next prev parent reply other threads:[~2017-06-08 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 9:57 next-20170608 build: 1 failures 4 warnings (next-20170608) Build bot for Mark Brown
2017-06-08 10:27 ` Stephen Rothwell
2017-06-08 14:16 ` David Miller
2017-06-08 10:32 ` Mark Brown
2017-06-08 11:33 ` Sebastian Reichel
2017-06-08 14:17 ` David Miller [this message]
2017-06-08 14:53 ` Sebastian Reichel
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=20170608.101757.1257358800507365931.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sre@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