From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Daniel Golle <daniel@makrotopia.org>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>,
Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 00/15] rt2x00: OpenWrt patches improving MT7620
Date: Sat, 17 Sep 2022 15:24:45 +0200 [thread overview]
Message-ID: <20220917132445.GO17901@wp.pl> (raw)
In-Reply-To: <20220917131733.GM17901@wp.pl>
On Sat, Sep 17, 2022 at 03:17:35PM +0200, Stanislaw Gruszka wrote:
> On Sat, Sep 17, 2022 at 12:03:57AM +0100, Daniel Golle wrote:
> > Over the years we have been accumulating a number of patches improving
> > support for the IEEE 802.11bgn 2T2R wireless interface built into the
> > MediaTek MT7620 MIPS SoCs. Many of them have not been in shape for
> > being submitted to Linux and changes were needed to make checkpatch.pl
> > all happy. Now they look as good as it gets, given that most code deals
> > with undocumented registers and was adapted from the vendor driver.
> >
> > Patch 1/1 also has been previously submitted and then (imho wrongly)
> >rejected, so I've included it in this series.
>
> In general this looks good. Some calibration functions are just too
> big, but we can eventually take them and refactor in the tree.
> Just please assure there are no compilation warnings and add
> yours signed-off by to all patches.
Also please configure git-send-email to send patches in one thread.
Thanks
Stanislaw
prev parent reply other threads:[~2022-09-17 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 23:03 [PATCH 00/15] rt2x00: OpenWrt patches improving MT7620 Daniel Golle
2022-09-17 13:17 ` Stanislaw Gruszka
2022-09-17 13:24 ` Stanislaw Gruszka [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=20220917132445.GO17901@wp.pl \
--to=stf_xl@wp.pl \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=helmut.schaa@googlemail.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pabeni@redhat.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).