Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "naamax.meir" <naamax.meir@linux.intel.com>
To: Sasha Neftin <sasha.neftin@intel.com>, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH v1 1/1] igc: Remove forced_speed_duplex value
Date: Tue, 19 Jul 2022 10:05:49 +0300	[thread overview]
Message-ID: <d9233529-4df9-ff17-2f29-3dd5177779e7@linux.intel.com> (raw)
In-Reply-To: <20220718095015.3243215-1-sasha.neftin@intel.com>

On 7/18/2022 12:50, Sasha Neftin wrote:
> u8 forced_speed_duplex from value from igc_mac_info struct is not used.
> This patch comes to tidy up the driver code.
> 
> Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
> ---
>   drivers/net/ethernet/intel/igc/igc_hw.h | 2 --
>   1 file changed, 2 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

      reply	other threads:[~2022-07-19  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:50 [Intel-wired-lan] [PATCH v1 1/1] igc: Remove forced_speed_duplex value Sasha Neftin
2022-07-19  7:05 ` naamax.meir [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=d9233529-4df9-ff17-2f29-3dd5177779e7@linux.intel.com \
    --to=naamax.meir@linux.intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --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