From: Vladimir Oltean <olteanv@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Nikolay Aleksandrov <nikolay@nvidia.com>,
kbuild-all@lists.01.org, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [net-next:master 38/46] net/bridge/br_device.c:96:7: error: too many arguments to function 'br_multicast_querier_exists'
Date: Sun, 1 Nov 2020 02:10:10 +0200 [thread overview]
Message-ID: <20201101001010.t7y26ozvh2v3xjyc@skbuf> (raw)
In-Reply-To: <202011010816.xqRrTSz5-lkp@intel.com>
On Sun, Nov 01, 2020 at 08:00:18AM +0800, kernel test robot wrote:
> >> net/bridge/br_device.c:96:7: error: too many arguments to function 'br_multicast_querier_exists'
Oops, I sent this patch as a fixup:
https://patchwork.ozlabs.org/project/netdev/patch/20201101000845.190009-1-vladimir.oltean@nxp.com/
prev parent reply other threads:[~2020-11-01 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 0:00 [net-next:master 38/46] net/bridge/br_device.c:96:7: error: too many arguments to function 'br_multicast_querier_exists' kernel test robot
2020-11-01 0:10 ` Vladimir Oltean [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=20201101001010.t7y26ozvh2v3xjyc@skbuf \
--to=olteanv@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=vladimir.oltean@nxp.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