From: Felix Fietkau <nbd@nbd.name>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull request: mt76 2019-05-22
Date: Fri, 29 May 2020 18:26:18 +0200 [thread overview]
Message-ID: <adcaf365-8dda-8c04-99ab-c6d1d1901fc8@nbd.name> (raw)
In-Reply-To: <875zceu90v.fsf@codeaurora.org>
On 2020-05-29 16:10, Kalle Valo wrote:
> Felix Fietkau <nbd@nbd.name> writes:
>
>> Hi Kalle,
>>
>> here's another pull request for 5.8, replacing the previous one.
>>
>> - Felix
>>
>> The following changes since commit 50ce4c099bebf56be86c9448f7f4bcd34f33663c:
>>
>> sctp: fix typo sctp_ulpevent_nofity_peer_addr_change (2020-05-27 15:08:02 -0700)
>>
>> are available in the Git repository at:
>>
>> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2020-05-28
>>
>> for you to fetch changes up to d9045b18cd445e0d0a53903ffd5d79793d9df59e:
>>
>> mt76: mt7915: remove set but not used variable 'msta' (2020-05-28 17:57:25 +0200)
>>
>> ----------------------------------------------------------------
>> mt76 patches for 5.8
>>
>> * fixes for sparse warnings
>> * DBDC fixes
>> * mt7663 remain-on-channel support
>> * mt7915 spatial reuse support
>> * mt7915 radiotap fix
>> * station wcid allocation fix
>> * mt7663 powersave fix
>> * mt7663 scan fix
>> * mt7611n support
>> * cleanup
>>
>> ----------------------------------------------------------------
>
> One commit has the Cc field by accident, but no need to resend because
> of this. Just check your workflow.
Sorry about that. I will be more careful about that sort of thing.
Thanks,
- Felix
next prev parent reply other threads:[~2020-05-29 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 16:06 pull request: mt76 2019-05-22 Felix Fietkau
2020-05-29 14:10 ` Kalle Valo
2020-05-29 16:26 ` Felix Fietkau [this message]
2020-05-29 17:42 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2020-05-22 12:51 Felix Fietkau
2020-05-27 5:48 ` 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=adcaf365-8dda-8c04-99ab-c6d1d1901fc8@nbd.name \
--to=nbd@nbd.name \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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 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.