From: Simon Horman <horms@kernel.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mschmidt@redhat.com,
aleksandr.loktionov@intel.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [PATCH iwl-next v2 1/7] i40e: Remove flags field from i40e_veb
Date: Thu, 28 Mar 2024 17:23:09 +0000 [thread overview]
Message-ID: <20240328172309.GB651713@kernel.org> (raw)
In-Reply-To: <20240327075733.8967-2-ivecera@redhat.com>
On Wed, Mar 27, 2024 at 08:57:27AM +0100, Ivan Vecera wrote:
> The field is initialized always to zero and it is never read.
> Remove it.
>
> Reviewed-by: Michal Schmidt <mschmidt@redhat.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> Reviewed-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-03-28 17:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 7:57 [PATCH iwl-next v2 0/7] i40e: cleanups & refactors Ivan Vecera
2024-03-27 7:57 ` [PATCH iwl-next v2 1/7] i40e: Remove flags field from i40e_veb Ivan Vecera
2024-03-28 17:23 ` Simon Horman [this message]
2024-04-02 4:20 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-03-27 7:57 ` [PATCH iwl-next v2 2/7] i40e: Refactor argument of several client notification functions Ivan Vecera
2024-03-28 17:22 ` Simon Horman
2024-03-27 7:57 ` [PATCH iwl-next v2 3/7] i40e: Refactor argument of i40e_detect_recover_hung() Ivan Vecera
2024-03-28 17:23 ` Simon Horman
2024-03-29 4:47 ` Kalesh Anakkur Purayil
2024-03-29 11:02 ` [Intel-wired-lan] " Loktionov, Aleksandr
2024-04-02 4:21 ` Pucha, HimasekharX Reddy
2024-03-27 7:57 ` [PATCH iwl-next v2 4/7] i40e: Add helper to access main VSI Ivan Vecera
2024-03-28 17:24 ` Simon Horman
2024-04-02 4:23 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-03-27 7:57 ` [PATCH iwl-next v2 5/7] i40e: Consolidate checks whether given VSI is main Ivan Vecera
2024-03-28 17:24 ` Simon Horman
2024-04-02 4:25 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-03-27 7:57 ` [PATCH iwl-next v2 6/7] i40e: Add helper to access main VEB Ivan Vecera
2024-03-28 17:24 ` Simon Horman
2024-04-02 4:33 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-03-27 7:57 ` [PATCH iwl-next v2 7/7] i40e: Add and use helper to reconfigure TC for given VSI Ivan Vecera
2024-03-28 17:25 ` Simon Horman
2024-04-12 14:19 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-04-12 21:19 ` [PATCH iwl-next v2 0/7] i40e: cleanups & refactors Tony Nguyen
2024-04-26 17:16 ` Ivan Vecera
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=20240328172309.GB651713@kernel.org \
--to=horms@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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).