From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Ingyu Jang <ingyujang25@korea.ac.kr>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH iwl-next] ixgbe: make EEPROM init_params() return void
Date: Thu, 5 Nov 2026 14:49:47 +0100 [thread overview]
Message-ID: <a0d74537-a397-4e3e-b77b-38ef2b9cd194@intel.com> (raw)
In-Reply-To: <20261101234725.1414173-1-ingyujang25@korea.ac.kr>
On 11/2/26 12:47 AM, Ingyu Jang wrote:
> All implementations of the EEPROM init_params() operation always
> return 0, so the error checks on its return value in ixgbe_sw_init()
> and the E610 NVM helpers never trigger.
>
> Make init_params() return void and remove the dead checks.
>
> Link: https://lore.kernel.org/all/8524c812-b659-4670-b370-35682aba2d2f@intel.com
> Signed-off-by: Ingyu Jang <ingyujang25@korea.ac.kr>
thank you for reaching out,
in general we don't want trivial refactors unless as a part of bigger
contribution
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#clean-up-patches
especially now, we are drowned in patches, so this particular one would
be on the very bottom of the priority list
> ---
> .../net/ethernet/intel/ixgbe/ixgbe_common.c | 4 +--
> .../net/ethernet/intel/ixgbe/ixgbe_common.h | 2 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c | 29 +++++--------------
> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.h | 2 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 5 +---
> drivers/net/ethernet/intel/ixgbe/ixgbe_type.h | 2 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_x540.c | 4 +--
> drivers/net/ethernet/intel/ixgbe/ixgbe_x540.h | 2 +-
> drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 4 +--
> 9 files changed, 16 insertions(+), 38 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_common.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_common.c
> index 3ea6765f9c5d8..ab2c0818f2417 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_common.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_common.c
> @@ -857,7 +857,7 @@ int ixgbe_led_off_generic(struct ixgbe_hw *hw, u32 index)
> * Initializes the EEPROM parameters ixgbe_eeprom_info within the
> * ixgbe_hw struct in order to set up EEPROM access.
> **/
> -int ixgbe_init_eeprom_params_generic(struct ixgbe_hw *hw)
> +void ixgbe_init_eeprom_params_generic(struct ixgbe_hw *hw)
> {
> struct ixgbe_eeprom_info *eeprom = &hw->eeprom;
> u32 eec;
> @@ -895,8 +895,6 @@ int ixgbe_init_eeprom_params_generic(struct ixgbe_hw *hw)
> hw_dbg(hw, "Eeprom params: type = %d, size = %d, address bits: %d\n",
> eeprom->type, eeprom->word_size, eeprom->address_bits);
> }
> -
> - return 0;
> }
>
[...]
prev parent reply other threads:[~2026-11-05 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:47 Ingyu Jang
2026-11-05 13:49 ` Przemek Kitszel [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=a0d74537-a397-4e3e-b77b-38ef2b9cd194@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=ingyujang25@korea.ac.kr \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®