All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: David Poole <dpoole@cradlepoint.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Ben Greear <greearb@candelatech.com>,
	John Crispin <john@phrozen.org>
Subject: Re: [PATCH 0/4] iw: add HE capabilities scan parsing
Date: Thu, 19 Nov 2020 11:20:39 -0800	[thread overview]
Message-ID: <CA+ASDXNoVq6JBsoEHHsXT0Aps=SgLw4f0W8EMCbkp78vcNCLxw@mail.gmail.com> (raw)
In-Reply-To: <DM5PR12MB1801E9BD703DB5E6381CF602D9E00@DM5PR12MB1801.namprd12.prod.outlook.com>

On Thu, Nov 19, 2020 at 7:06 AM David Poole <dpoole@cradlepoint.com> wrote:
> I'll be happy to help test!

You're more than welcome to :) Feel free to reply back here with
positive or negative feedback. (And if positive, might as well make
that a "Tested-by: Your Name <your@email.tld>".) I have more HE
clients than APs, so I only have limited test coverage for the "scan"
part.

Brian

      reply	other threads:[~2020-11-19 19:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18  3:39 [PATCH 0/4] iw: add HE capabilities scan parsing Brian Norris
2020-11-18  3:39 ` [PATCH 1/4] iw: scan: add extension tag parsing Brian Norris
2020-11-18  3:39 ` [PATCH 2/4] iw: util: factor out HE capability parser Brian Norris
2020-11-18  3:39 ` [PATCH 3/4] iw: scan: parse HE capabilities Brian Norris
2020-11-18  3:39 ` [PATCH 4/4] iw: scan: fixup HE caps whitespace Brian Norris
2020-11-19 15:06 ` [PATCH 0/4] iw: add HE capabilities scan parsing David Poole
2020-11-19 19:20   ` Brian Norris [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='CA+ASDXNoVq6JBsoEHHsXT0Aps=SgLw4f0W8EMCbkp78vcNCLxw@mail.gmail.com' \
    --to=briannorris@chromium.org \
    --cc=dpoole@cradlepoint.com \
    --cc=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=john@phrozen.org \
    --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.