From: kbuild test robot <lkp@intel.com>
To: Sameeh Jubran <sameehj@amazon.com>
Cc: kbuild-all@01.org, Netanel Belgazal <netanel@amazon.com>,
Saeed Bishara <saeedb@amazon.com>,
Zorik Machulsky <zorik@amazon.com>,
Arthur Kiyanovski <akiyano@amazon.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] net: ena: ena_adjust_intr_moderation() can be static
Date: Fri, 14 Jun 2019 11:02:08 +0800 [thread overview]
Message-ID: <20190614030208.GA13281@lkp-kbuild18> (raw)
In-Reply-To: <201906141113.NUYnC1ZG%lkp@intel.com>
Fixes: c2b542044761 ("net: ena: remove inline keyword from functions in *.c")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
ena_netdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/amazon/ena/ena_netdev.c b/drivers/net/ethernet/amazon/ena/ena_netdev.c
index b7865ee..b63ae9b 100644
--- a/drivers/net/ethernet/amazon/ena/ena_netdev.c
+++ b/drivers/net/ethernet/amazon/ena/ena_netdev.c
@@ -1155,7 +1155,7 @@ static int ena_clean_rx_irq(struct ena_ring *rx_ring, struct napi_struct *napi,
return 0;
}
-void ena_adjust_intr_moderation(struct ena_ring *rx_ring,
+static void ena_adjust_intr_moderation(struct ena_ring *rx_ring,
struct ena_ring *tx_ring)
{
/* We apply adaptive moderation on Rx path only.
prev parent reply other threads:[~2019-06-14 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 3:02 [linux-next:master 5930/6350] drivers/net/ethernet/amazon/ena/ena_netdev.c:1158:6: sparse: sparse: symbol 'ena_adjust_intr_moderation' was not declared. Should it be static? kbuild test robot
2019-06-14 3:02 ` kbuild test robot [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=20190614030208.GA13281@lkp-kbuild18 \
--to=lkp@intel.com \
--cc=akiyano@amazon.com \
--cc=edumazet@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=sameehj@amazon.com \
--cc=zorik@amazon.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).