From: Loic Poulain <loic.poulain@linaro.org>
To: Ramon Fried <ramon.fried@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/6] wcn36xx misc fixes
Date: Fri, 24 Jul 2020 16:02:24 +0200 [thread overview]
Message-ID: <CAMZdPi8jgoYsWd6d90WE-sGD8P5LMKO+YAHoP5-xRBV+vncy=A@mail.gmail.com> (raw)
In-Reply-To: <CA+Kvs9mV39gndidkDjMHswQGii74MH4cTDr9az1HLNOtW6PZTA@mail.gmail.com>
Hi Ramon,
On Fri, 24 Jul 2020 at 15:47, Ramon Fried <ramon.fried@gmail.com> wrote:
>
> On Fri, Jul 24, 2020 at 1:15 PM Loic Poulain <loic.poulain@linaro.org> wrote:
> >
> > This series contains various fixes for the wcn36xx driver.
> > This has been tested with wcn3620, wcn3660 and wcn3680.
> >
> > v2: - Move TX retries change into its own commit
> > - Additional patch for sequence number assignment
> > - Reword TX ack commit log (timeout detection)
> > - Fix checkpatch issues reported by Bryan
> >
> > Loic Poulain (6):
> > wcn36xx: Fix multiple AMPDU sessions support
> > wcn36xx: Add TX ack support
> > wcn36xx: Increase number of TX retries
> > wcn36xx: Fix TX data path
> > wcn36xx: Fix software-driven scan
> > wcn36xx: Use sequence number allocated by mac80211
> >
> > drivers/net/wireless/ath/wcn36xx/dxe.c | 57 +++++++++-
> > drivers/net/wireless/ath/wcn36xx/main.c | 172 +++++++++++++++--------------
> > drivers/net/wireless/ath/wcn36xx/smd.c | 59 ++++++++--
> > drivers/net/wireless/ath/wcn36xx/smd.h | 12 +-
> > drivers/net/wireless/ath/wcn36xx/txrx.c | 57 ++++++----
> > drivers/net/wireless/ath/wcn36xx/wcn36xx.h | 7 +-
> > 6 files changed, 241 insertions(+), 123 deletions(-)
> >
> > --
> > 2.7.4
> >
> >
> > _______________________________________________
> > wcn36xx mailing list
> > wcn36xx@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/wcn36xx
>
>
> Hi Loic,
> What about upstreaming the fixes for several TP-Link AP's ?
> The WCN36xx is not usable on those networks and your own tree patches seems to
> be working properly.
Which ones do you have in mind?
This series normally contains the most important (and clean) patches.
Cheers,
Loic
next prev parent reply other threads:[~2020-07-24 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:20 [PATCH v2 0/6] wcn36xx misc fixes Loic Poulain
2020-07-24 10:20 ` [PATCH v2 1/6] wcn36xx: Fix multiple AMPDU sessions support Loic Poulain
2020-08-14 15:02 ` Kalle Valo
2020-07-24 10:20 ` [PATCH v2 2/6] wcn36xx: Add TX ack support Loic Poulain
2020-07-24 10:20 ` [PATCH v2 3/6] wcn36xx: Increase number of TX retries Loic Poulain
[not found] ` <CA+Kvs9nZm+uoRJfjq33s1_nTbPt82NnEKmgYCWk0q5vH+-ca9w@mail.gmail.com>
2020-07-24 13:12 ` Kalle Valo
2020-07-24 13:43 ` Ramon Fried
2020-07-24 10:20 ` [PATCH v2 4/6] wcn36xx: Fix TX data path Loic Poulain
2020-07-24 10:20 ` [PATCH v2 5/6] wcn36xx: Fix software-driven scan Loic Poulain
2020-07-29 23:03 ` Bryan O'Donoghue
2020-08-14 14:50 ` Kalle Valo
2020-07-24 10:20 ` [PATCH v2 6/6] wcn36xx: Use sequence number allocated by mac80211 Loic Poulain
2020-07-24 13:47 ` [PATCH v2 0/6] wcn36xx misc fixes Ramon Fried
2020-07-24 14:02 ` Loic Poulain [this message]
2020-07-24 18:51 ` Ramon Fried
2020-07-28 10:13 ` Loic Poulain
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='CAMZdPi8jgoYsWd6d90WE-sGD8P5LMKO+YAHoP5-xRBV+vncy=A@mail.gmail.com' \
--to=loic.poulain@linaro.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ramon.fried@gmail.com \
--cc=wcn36xx@lists.infradead.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 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).