From: Nikolay Aleksandrov <nikolay@nvidia.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
kernel test robot <lkp@intel.com>
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>,
kbuild-all@lists.01.org, Netdev <netdev@vger.kernel.org>,
linux-mips@vger.kernel.org,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Roopa Prabhu" <roopa@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
bridge@lists.linux-foundation.org
Subject: Re: [net-next:master 40/65] net/bridge/br_input.c:135:8: error: too many arguments to function 'br_multicast_is_router'
Date: Fri, 14 May 2021 13:12:12 +0300 [thread overview]
Message-ID: <7dde3521-3df5-8b65-b6a9-c974b84ab0eb@nvidia.com> (raw)
In-Reply-To: <CA+G9fYuSVLOOu0aEs1bm5myxDMGe1VK_MVm61BmY3dwDx_yRmA@mail.gmail.com>
On 14/05/2021 13:06, Naresh Kamboju wrote:
> [Please ignore this email if you already know these build failures]
>
> + Adding maintainers
>
> On Fri, 14 May 2021 at 06:35, kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
>> head: ea89c862f01e02ec459932c7c3113fa37aedd09a
>> commit: 1a3065a26807b4cdd65d3b696ddb18385610f7da [40/65] net: bridge: mcast: prepare is-router function for mcast router split
>> config: um-randconfig-s032-20210514 (attached as .config)
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>> reproduce:
>> # apt-get install sparse
>> # sparse version: v0.6.3-341-g8af24329-dirty
>> # https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=1a3065a26807b4cdd65d3b696ddb18385610f7da
>> git remote add net-next https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>> git fetch --no-tags net-next master
>> git checkout 1a3065a26807b4cdd65d3b696ddb18385610f7da
>> # save the attached .config to linux build tree
>> make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=um
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> net/bridge/br_input.c: In function 'br_handle_frame_finish':
>>>> net/bridge/br_input.c:135:8: error: too many arguments to function 'br_multicast_is_router'
>> 135 | br_multicast_is_router(br, skb)) {
>> | ^~~~~~~~~~~~~~~~~~~~~~
>> In file included from net/bridge/br_input.c:23:
>> net/bridge/br_private.h:1059:20: note: declared here
>> 1059 | static inline bool br_multicast_is_router(struct net_bridge *br)
>> | ^~~~~~~~~~~~~~~~~~~~~~
>>
I have already sent a patch for this one:
https://patchwork.kernel.org/project/netdevbpf/patch/20210514073233.2564187-1-razor@blackwall.org/
prev parent reply other threads:[~2021-05-14 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 1:04 [net-next:master 40/65] net/bridge/br_input.c:135:8: error: too many arguments to function 'br_multicast_is_router' kernel test robot
2021-05-14 10:06 ` Naresh Kamboju
2021-05-14 10:12 ` Nikolay Aleksandrov [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=7dde3521-3df5-8b65-b6a9-c974b84ab0eb@nvidia.com \
--to=nikolay@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).