Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jan Sokolowski <jan.sokolowski@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: remove rx_len_errors statistic
Date: Thu, 7 Dec 2023 15:33:10 -0800	[thread overview]
Message-ID: <7033167e-406d-b746-1495-cc4d3b085cdb@intel.com> (raw)
In-Reply-To: <20231206104333.141792-1-jan.sokolowski@intel.com>



On 12/6/2023 2:43 AM, Jan Sokolowski wrote:
> It was found that this statistic is incorrectly
> reported by HW and thus, useless.
> 
> As RX length error statistics are shown to the
> end user when requested, the values reported
> are misleading.
> 
> Thus, that value is no longer reported and
> doesn't count anymore when adding all rx errors.
> 
> Signed-off-by: Jan Sokolowski <jan.sokolowski@intel.com>
> Reviewed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>

Applied, however, shouldn't this have been a v2?

https://lore.kernel.org/intel-wired-lan/20231120112726.149409-1-jan.sokolowski@intel.com/
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-12-07 23:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 10:43 [Intel-wired-lan] [PATCH iwl-next v1] ice: remove rx_len_errors statistic Jan Sokolowski
2023-12-07 23:33 ` Tony Nguyen [this message]
2023-12-11  4:58 ` Pucha, HimasekharX Reddy
  -- strict thread matches above, loose matches on Subject: below --
2023-11-20 11:27 Jan Sokolowski
2023-11-20 21:48 ` Jacob Keller
2023-11-29 10:26   ` Sokolowski, Jan
2023-11-29 11:03     ` Przemek Kitszel

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=7033167e-406d-b746-1495-cc4d3b085cdb@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jan.sokolowski@intel.com \
    --cc=mateusz.polchlopek@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