From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
linux- stable <stable@vger.kernel.org>,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
lkft-triage@lists.linaro.org,
"David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: stable-rc 4.14 : net/ipv6/addrconf.c:6593:22: error: 'blackhole_netdev' undeclared
Date: Mon, 4 Nov 2019 12:13:45 -0500 [thread overview]
Message-ID: <20191104171345.GG4787@sasha-vm> (raw)
In-Reply-To: <20191104133258.GA2130866@kroah.com>
On Mon, Nov 04, 2019 at 02:32:58PM +0100, Greg Kroah-Hartman wrote:
>On Mon, Nov 04, 2019 at 06:44:39PM +0530, Naresh Kamboju wrote:
>> stable-rc 4.14 for architectures arm64, arm, x86_64 and i386 builds
>> failed due to below error,
>>
>> net/ipv6/addrconf.c: In function 'addrconf_init':
>> net/ipv6/addrconf.c:6593:22: error: 'blackhole_netdev' undeclared
>> (first use in this function); did you mean 'alloc_netdev'?
>> bdev = ipv6_add_dev(blackhole_netdev);
>> ^~~~~~~~~~~~~~~~
>> alloc_netdev
>> net/ipv6/addrconf.c:6593:22: note: each undeclared identifier is
>> reported only once for each function it appears in
>> net/ipv6/addrconf.c: In function 'addrconf_cleanup':
>> net/ipv6/addrconf.c:6667:18: error: 'blackhole_netdev' undeclared
>> (first use in this function); did you mean 'alloc_netdev'?
>> addrconf_ifdown(blackhole_netdev, 2);
>> ^~~~~~~~~~~~~~~~
>> alloc_netdev
>>
>> Build link,
>> https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-stable-rc-4.14/DISTRO=lkft,MACHINE=intel-corei7-64,label=docker-lkft/632/consoleText
>>
>
>Ick, my fault, will go fix this, sorry about that.
I've dropped this patch from 5.3 too, it was reverted upstream.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-11-04 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 13:14 stable-rc 4.14 : net/ipv6/addrconf.c:6593:22: error: 'blackhole_netdev' undeclared Naresh Kamboju
2019-11-04 13:32 ` Greg Kroah-Hartman
2019-11-04 17:13 ` Sasha Levin [this message]
2019-11-04 20:32 ` Greg Kroah-Hartman
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=20191104171345.GG4787@sasha-vm \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.