From: kbuild test robot <lkp@intel.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, "Björn Töpel" <bjorn.topel@intel.com>,
bpf@vger.kernel.org, magnus.karlsson@gmail.com,
magnus.karlsson@intel.com, jonathan.lemon@gmail.com,
ecree@solarflare.com, thoiland@redhat.com,
andrii.nakryiko@gmail.com
Subject: [RFC PATCH] i40e: ____xdp_call_i40e_xdp_call_tramp can be static
Date: Sat, 23 Nov 2019 23:52:21 +0800 [thread overview]
Message-ID: <20191123155221.s32llr6jsoxtdmoc@4978f4969bb8> (raw)
In-Reply-To: <20191119160757.27714-4-bjorn.topel@gmail.com>
Fixes: cfbcb56c2871 ("i40e: start using xdp_call.h")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
i40e_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c
index 59b530e4198f2..6771d77871152 100644
--- a/drivers/net/ethernet/intel/i40e/i40e_main.c
+++ b/drivers/net/ethernet/intel/i40e/i40e_main.c
@@ -12518,7 +12518,7 @@ static netdev_features_t i40e_features_check(struct sk_buff *skb,
return features & ~(NETIF_F_CSUM_MASK | NETIF_F_GSO_MASK);
}
-DEFINE_XDP_CALL(i40e_xdp_call);
+static DEFINE_XDP_CALL(i40e_xdp_call);
/**
* i40e_xdp_setup - add/remove an XDP program
prev parent reply other threads:[~2019-11-23 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 16:07 [PATCH bpf-next 0/3] Introduce xdp_call.h and the BPF dispatcher Björn Töpel
2019-11-19 16:07 ` [PATCH bpf-next 1/3] bpf: introduce " Björn Töpel
2019-11-21 7:27 ` kbuild test robot
2019-11-21 9:23 ` Björn Töpel
2019-11-23 0:25 ` [RFC PATCH] bpf: bpf_dispatcher_lookup() can be static kbuild test robot
2019-11-23 14:03 ` kbuild test robot
2019-11-19 16:07 ` [PATCH bpf-next 2/3] xdp: introduce xdp_call Björn Töpel
2019-11-19 16:07 ` [PATCH bpf-next 3/3] i40e: start using xdp_call.h Björn Töpel
2019-11-23 15:52 ` kbuild test robot
2019-11-23 15:52 ` 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=20191123155221.s32llr6jsoxtdmoc@4978f4969bb8 \
--to=lkp@intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ecree@solarflare.com \
--cc=jonathan.lemon@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=thoiland@redhat.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).