From: Kalle Valo <kvalo@codeaurora.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request: mt76 2019-01-27
Date: Wed, 29 Jan 2020 16:00:58 +0200 [thread overview]
Message-ID: <87o8um8iqt.fsf@codeaurora.org> (raw)
In-Reply-To: <ec25181f-3a2e-0374-a30e-2744e247aea6@nbd.name> (Felix Fietkau's message of "Mon, 27 Jan 2020 19:22:06 +0100")
Felix Fietkau <nbd@nbd.name> writes:
> here's my pull request for 5.6
>
> - Felix
>
> The following changes since commit 2a13513f99e735184fd6f889d78da6424fda80a1:
>
> Merge ath-next from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2020-01-26 17:54:46 +0200)
>
> are available in the Git repository at:
>
> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2020-01-27
>
> for you to fetch changes up to bc6ea8c1cf22ef97d8ece12c433138af2f6e7573:
>
> mt76: enable Airtime Queue Limit support (2020-01-27 19:17:16 +0100)
>
> ----------------------------------------------------------------
> mt76 patches for 5.6
>
> * dual-band concurrent support for MT7615
> * fixes for rx path race conditions
> * EEPROM fixes
> * MAC address handling fixes
> * coverage class support for MT7615
> * beacon fixes for USB devices
> * MT7615 LED support
> * minor cleanups/fixes for all drivers
> * set_antenna support for MT7615
> * tracing improvements
> * preparation for supporting new USB devices
>
> ----------------------------------------------------------------
Sorry, too late. Linus released v5.5 on Sunday which opened the merge
window for v5.6. And I need to get everything ready for net-next before
the merge window opens.
So this has to wait for v5.7 and I'll pull this after the merge window
has closed.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-01-29 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 18:22 pull request: mt76 2019-01-27 Felix Fietkau
2020-01-29 14:00 ` Kalle Valo [this message]
2020-01-30 12:09 ` Felix Fietkau
2020-01-30 13:44 ` Kalle Valo
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=87o8um8iqt.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).