From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: maxime.chevallier@bootlin.com, kbuild-all@01.org,
netdev@vger.kernel.org, antoine.tenart@bootlin.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next] net: mvpp2: mvpp2_cls_flow_get() can be static
Date: Fri, 13 Jul 2018 20:22:21 -0700 (PDT) [thread overview]
Message-ID: <20180713.202221.1032240013171097775.davem@davemloft.net> (raw)
In-Reply-To: <20180714012735.GA24562@lkp-sb05>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Sat, 14 Jul 2018 09:27:35 +0800
> Fixes: f9358e12a0af ("net: mvpp2: split ingress traffic into multiple flows")
> Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
Applied, thank you.
prev parent reply other threads:[~2018-07-14 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 1:27 [net-next:master 597/618] drivers/net/ethernet/marvell/mvpp2/mvpp2_cls.c:444:23: sparse: symbol 'mvpp2_cls_flow_get' was not declared. Should it be static? kbuild test robot
2018-07-14 1:27 ` [RFC PATCH net-next] net: mvpp2: mvpp2_cls_flow_get() can be static kbuild test robot
2018-07-14 3:22 ` David Miller [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=20180713.202221.1032240013171097775.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=antoine.tenart@bootlin.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).