From: Brian Norris <briannorris@chromium.org>
To: Tony Chuang <yhchuang@realtek.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Andy Huang <tehuang@realtek.com>
Subject: Re: [PATCH v7 1/2] rtw88: add regulatory process strategy for different chipset
Date: Tue, 31 Mar 2020 15:30:10 -0700 [thread overview]
Message-ID: <CA+ASDXP0QMv=P6p-GRd4skhYdReHV=crvRz74HyyMXtSAHrCaQ@mail.gmail.com> (raw)
In-Reply-To: <20200327075229.29191-2-yhchuang@realtek.com>
On Fri, Mar 27, 2020 at 12:52 AM <yhchuang@realtek.com> wrote:
> v3 -> v4
> * squashed with "rtw88: support dynamic user regulatory setting"
> * modify the commit log
>
> v4 -> v5
> * no change
>
> v5 -> v6
> * remove custom world-wide, use stack world-wide
> * surface error codes
>
> v6 -> v7
> * restore custom world-wide
> * modify commit message to be more clear
If it wasn't clear, v7 looks more like v5. I think I had some of my
own misunderstanding of the regulatory core when
reading/reviewing/testing v5, which resulted in ill-conceived changes
in v6. I think I've gotten my head around this, and this looks fine to
me. But that's not saying much, given how confused I was at times.
Reviewed-by: Brian Norris <briannorris@chromium.org>
next prev parent reply other threads:[~2020-03-31 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:52 [PATCH v7 0/2] rtw88: update regulatory settings yhchuang
2020-03-27 7:52 ` [PATCH v7 1/2] rtw88: add regulatory process strategy for different chipset yhchuang
2020-03-31 22:30 ` Brian Norris [this message]
2020-03-27 7:52 ` [PATCH v7 2/2] rtw88: add adaptivity support for EU/JP regulatory yhchuang
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+ASDXP0QMv=P6p-GRd4skhYdReHV=crvRz74HyyMXtSAHrCaQ@mail.gmail.com' \
--to=briannorris@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tehuang@realtek.com \
--cc=yhchuang@realtek.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).