All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wifi: iwlwifi: add ethtool tx and rx stats.
Date: Tue, 23 May 2023 17:26:18 +0200	[thread overview]
Message-ID: <ZGzbGmaJld0eA1BF@corigine.com> (raw)
In-Reply-To: <adf58b64-f1dc-82a0-ae37-4dbe8b53f3bc@candelatech.com>

On Tue, May 23, 2023 at 07:50:22AM -0700, Ben Greear wrote:
> On 5/23/23 3:32 AM, Simon Horman wrote:
> > On Mon, May 22, 2023 at 04:37:43PM -0700, greearb@candelatech.com wrote:
> > > From: Ben Greear <greearb@candelatech.com>
> > > 
> > > Report tx/rx error codes, nss, mcs, bandwidth, mode, he types,
> > > tx ampdu length histogram.
> > > 
> > > To provide some clues about how transmit and receive path is
> > > actually working.
> > > 
> > > Signed-off-by: Ben Greear <greearb@candelatech.com>
> > > ---
> > > 
> > > v3:  Combine tx and rx ethtool patches into single patch.
> > > Fix some stats calculations, especially the path that consumes
> > > tx frames based on block-ack receipt.
> > > 
> > > Comparing the stats with expected values now matches better, but
> > > hard to verify everything exactly.
> > 
> > Hi Ben,
> > 
> > I am a little (lot) confused about what tree/branch this patch applies to.
> > 
> 
> It is against upstream iwlwifi-backports driver.  I need to use that to
> use latest Intel radio, and in general flow of patches seems to be
> iwlwif-backports -> kernel, so I was hoping the patch had a chance that
> way.  I'm sure it could also be patched into the kernel with a bit of
> work, and I'll be happy to do that work if that will make patch
> acceptable.

Thanks Ben,

got it.

      reply	other threads:[~2023-05-23 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 23:37 [PATCH v3] wifi: iwlwifi: add ethtool tx and rx stats greearb
2023-05-23 10:32 ` Simon Horman
2023-05-23 14:50   ` Ben Greear
2023-05-23 15:26     ` Simon Horman [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=ZGzbGmaJld0eA1BF@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.