From: Kalle Valo <kvalo@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request: mt76 2021-12-18 v2
Date: Mon, 20 Dec 2021 20:39:27 +0200 [thread overview]
Message-ID: <87mtkv9l40.fsf@codeaurora.org> (raw)
In-Reply-To: <de06ccae-1983-33bf-7cb2-908aee6b2412@nbd.name> (Felix Fietkau's message of "Sun, 19 Dec 2021 15:27:32 +0100")
Felix Fietkau <nbd@nbd.name> writes:
> Hi Kalle,
>
> here's my updated pull request for 5.17 with a compile fix for rebase issue
>
> - Felix
>
> The following changes since commit f75c1d55ecbadce027fd650d3ca79e357afae0d9:
>
> Merge tag 'wireless-drivers-next-2021-12-17' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next (2021-12-17 07:30:07 -0800)
>
> are available in the Git repository at:
>
> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2021-12-18
>
> for you to fetch changes up to b1460bb4eadf4b0bf5afe79fb4d25b9d985f2879:
>
> mt76: mt7921s: fix cmd timeout in throughput test (2021-12-19 15:24:05 +0100)
>
> ----------------------------------------------------------------
> mt76 patches for 5.17
>
> * decap offload fixes
> * mt7915 fixes
> * mt7921 fixes
> * eeprom fixes
> * powersave handling fixes
> * SAR support
> * code cleanups
>
> ----------------------------------------------------------------
Pulled, thanks.
I switched my email to kvalo@kernel.org and my codeaurora.org address
will stop working soon, please update your address book and scripts.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-12-20 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 14:27 pull request: mt76 2021-12-18 v2 Felix Fietkau
2021-12-20 18:39 ` Kalle Valo [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=87mtkv9l40.fsf@codeaurora.org \
--to=kvalo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.