From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, Sasha Neftin <sasha.neftin@intel.com>,
netdev@vger.kernel.org, Naama Meir <naamax.meir@linux.intel.com>
Subject: Re: [PATCH net-next 3/3] igc: Clean up and optimize watchdog task
Date: Thu, 26 Jan 2023 12:56:00 +0200 [thread overview]
Message-ID: <Y9JcQOcpMN+n4NH3@unreal> (raw)
In-Reply-To: <20230125212702.4030240-4-anthony.l.nguyen@intel.com>
On Wed, Jan 25, 2023 at 01:27:02PM -0800, Tony Nguyen wrote:
> From: Sasha Neftin <sasha.neftin@intel.com>
>
> i225/i226 parts used only one media type copper. The copper media type is
> not replaceable. Clean up the code accordingly, and remove the obsolete
> media replacement and reset options.
>
> Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
> Tested-by: Naama Meir <naamax.meir@linux.intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc.h | 2 --
> drivers/net/ethernet/intel/igc/igc_main.c | 17 -----------------
> 2 files changed, 19 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
prev parent reply other threads:[~2023-01-26 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 21:26 [PATCH net-next 0/3][pull request] Intel Wired LAN Driver Updates 2023-01-25 (igc) Tony Nguyen
2023-01-25 21:27 ` [PATCH net-next 1/3] igc: Add qbv_config_change_errors counter Tony Nguyen
2023-01-26 10:50 ` Leon Romanovsky
2023-01-25 21:27 ` [PATCH net-next 2/3] igc: offload queue max SDU from tc-taprio Tony Nguyen
2023-01-26 10:51 ` Leon Romanovsky
2023-02-07 13:38 ` Zulkifli, Muhammad Husaini
2023-01-25 21:27 ` [PATCH net-next 3/3] igc: Clean up and optimize watchdog task Tony Nguyen
2023-01-26 10:56 ` Leon Romanovsky [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=Y9JcQOcpMN+n4NH3@unreal \
--to=leon@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@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;
as well as URLs for NNTP newsgroup(s).