From: "Kadosh, MoriyaX" <moriyax.kadosh@intel.com>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
Keshav Goyal <keshav74123@gmail.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>
Cc: "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] igc: remove unreachable break after return in XDP path
Date: Mon, 19 Oct 2026 17:35:37 +0300 [thread overview]
Message-ID: <58ad6b76-fb79-4311-ae6f-981d436786d1@intel.com> (raw)
In-Reply-To: <IA3PR11MB8986F43DCC22F802B8236D18E5B62@IA3PR11MB8986.namprd11.prod.outlook.com>
On 03/09/2026 13:22, Loktionov, Aleksandr wrote:
>
>
>> -----Original Message-----
>> From: Keshav Goyal <keshav74123@gmail.com>
>> Sent: Wednesday, September 2, 2026 11:35 AM
>> To: Nguyen, Anthony L <anthony.l.nguyen@intel.com>; Kitszel,
>> Przemyslaw <przemyslaw.kitszel@intel.com>
>> Cc: andrew+netdev@lunn.ch; davem@davemloft.net; edumazet@google.com;
>> kuba@kernel.org; pabeni@redhat.com; intel-wired-lan@lists.osuosl.org;
>> netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Keshav Goyal
>> <keshav74123@gmail.com>
>> Subject: [PATCH net-next] igc: remove unreachable break after return
>> in XDP path
>>
>> The break statement after "return IGC_XDP_REDIRECT" in the XDP switch
>> case is dead code since the return exits the function unconditionally.
>> All other return statements in this switch are not followed by a
>> break.
>>
>> This was flagged by checkpatch.pl:
>> WARNING: break is not useful after a return
>>
>> Signed-off-by: Keshav Goyal <keshav74123@gmail.com>
>> ---
>> drivers/net/ethernet/intel/igc/igc_main.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/intel/igc/igc_main.c
>> b/drivers/net/ethernet/intel/igc/igc_main.c
>> index 1fb5f3cbe93c..3b7dd104d8d9 100644
>> --- a/drivers/net/ethernet/intel/igc/igc_main.c
>> +++ b/drivers/net/ethernet/intel/igc/igc_main.c
>> @@ -2525,7 +2525,6 @@ static int __igc_xdp_run_prog(struct igc_adapter
>> *adapter,
>> if (xdp_do_redirect(adapter->netdev, xdp, prog) < 0)
>> goto out_failure;
>> return IGC_XDP_REDIRECT;
>> - break;
>> default:
>> bpf_warn_invalid_xdp_action(adapter->netdev, prog, act);
>> fallthrough;
>> --
>> 2.55.0
>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Tested-by: Moriya Kadosh <moriyax.kadosh@intel.com>
prev parent reply other threads:[~2026-10-19 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:34 Keshav Goyal
2026-09-03 10:22 ` Loktionov, Aleksandr
2026-10-19 14:35 ` Kadosh, MoriyaX [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=58ad6b76-fb79-4311-ae6f-981d436786d1@intel.com \
--to=moriyax.kadosh@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=keshav74123@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®