From: Sid Hayn <sidhayn@gmail.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: stable@vger.kernel.org, Felix Fietkau <nbd@nbd.name>,
linux-wireless <linux-wireless@vger.kernel.org>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Subject: Re: [PATCH 4.20.x 0/7] mt76x0 fixes for 4.20 stable
Date: Mon, 28 Jan 2019 11:06:41 -0500 [thread overview]
Message-ID: <CAM0KTbBz4hLWuN5oAGJV9rXEGuHP1UDPsL2fYaKJA6pRJG1MDA@mail.gmail.com> (raw)
In-Reply-To: <1548160717-4059-1-git-send-email-sgruszka@redhat.com>
On Tue, Jan 22, 2019 at 7:41 AM Stanislaw Gruszka <sgruszka@redhat.com> wrote:
>
> There ware several bugs introduced in 4.20 development cycle
> for mt76x0 driver, that were fixed later but missed 4.20
> release. This patche set fixes issues for MT7610U and
> MT7630E.
>
> Bug reference:
> https://bugzilla.kernel.org/show_bug.cgi?id=202243
>
> Lorenzo Bianconi (1):
> mt76x0: phy: unify calibration between mt76x0u and mt76x0e
>
> Stanislaw Gruszka (6):
> mt76x0: do not overwrite other MT_BBP(AGC, 8) fields
> mt76x0: use band parameter for LC calibration
> mt76x02: run calibration after scanning
> mt76x02: assure we update gain after scan
> mt76x0: do not perform MCU calibration for MT7630
> mt76x0: antenna select corrections
>
> drivers/net/wireless/mediatek/mt76/mt76.h | 1 +
> drivers/net/wireless/mediatek/mt76/mt76x0/main.c | 9 +-
> drivers/net/wireless/mediatek/mt76/mt76x0/mt76x0.h | 5 +
> drivers/net/wireless/mediatek/mt76/mt76x0/phy.c | 170 +++++++--------------
> drivers/net/wireless/mediatek/mt76/mt76x0/usb.c | 1 +
> drivers/net/wireless/mediatek/mt76/mt76x02.h | 1 +
> .../net/wireless/mediatek/mt76/mt76x02_eeprom.h | 10 +-
> drivers/net/wireless/mediatek/mt76/mt76x02_phy.c | 1 +
> .../net/wireless/mediatek/mt76/mt76x2/usb_main.c | 3 +
> 9 files changed, 76 insertions(+), 125 deletions(-)
>
> --
> 1.9.3
>
Please forgive if I'm mistaken, but I haven't seen this hit the stable
queue or see any response at all. Did this get missed or just hasn't
been reached yet?
Thanks,
Zero
next prev parent reply other threads:[~2019-01-28 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 12:38 [PATCH 4.20.x 0/7] mt76x0 fixes for 4.20 stable Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 1/7] mt76x0: do not overwrite other MT_BBP(AGC, 8) fields Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 2/7] mt76x0: use band parameter for LC calibration Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 3/7] mt76x02: run calibration after scanning Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 4/7] mt76x02: assure we update gain after scan Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 5/7] mt76x0: do not perform MCU calibration for MT7630 Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 6/7] mt76x0: antenna select corrections Stanislaw Gruszka
2019-01-22 12:38 ` [PATCH 4.20.x 7/7] mt76x0: phy: unify calibration between mt76x0u and mt76x0e Stanislaw Gruszka
2019-01-28 16:06 ` Sid Hayn [this message]
2019-01-29 8:04 ` [PATCH 4.20.x 0/7] mt76x0 fixes for 4.20 stable Kalle Valo
2019-01-29 9:43 ` Greg KH
2019-01-29 15:55 ` Sid Hayn
2019-01-29 16:09 ` Greg KH
2019-01-29 10:29 ` Greg KH
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=CAM0KTbBz4hLWuN5oAGJV9rXEGuHP1UDPsL2fYaKJA6pRJG1MDA@mail.gmail.com \
--to=sidhayn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.com \
--cc=stable@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 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).