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 2021-06-18 v2
Date: Sat, 19 Jun 2021 09:28:13 +0200 [thread overview]
Message-ID: <aa6b2a81-4e52-4a5f-4253-8a54470e5270@nbd.name> (raw)
In-Reply-To: <87im2aic1j.fsf@codeaurora.org>
On 2021-06-19 08:49, Kalle Valo wrote:
> Felix Fietkau <nbd@nbd.name> writes:
>
>> Hi Kalle,
>>
>> here's an updated version of my first pull request for 5.14
>>
>> - Felix
>>
>> The following changes since commit 0c33795231bff5df410bd405b569c66851e92d4b:
>>
>> Merge tag 'wireless-drivers-next-2021-06-16' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next (2021-06-16 12:59:42 -0700)
>>
>> are available in the Git repository at:
>>
>> https://github.com/nbd168/wireless tags/mt76-for-kvalo-2021-06-18
>>
>> for you to fetch changes up to a7818339958c7d7940a102ccf88cf73260074344:
>>
>> mt76: mt7921: allow chip reset during device restart (2021-06-18 19:22:10 +0200)
>>
>> ----------------------------------------------------------------
>> mt76 patches for 5.14
>>
>> * mt7915 MSI support
>> * disable ASPM on mt7915
>> * mt7915 tx status reporting
>> * mt7921 decap offload
>> * driver fixes
>> * cleanups
>> * mt7921 runtime power management improvements
>> * testmode improvements/fixes
>> * runtime PM improvements
>>
>> ----------------------------------------------------------------
>
> Almost there :) But one commit is missing your s-o-b:
>
> ----------------------------------------------------------------------
> Commit
>
> 7c649aa4de81 ("mt76: move mt76_rates in mt76 module")
>
> is missing a Signed-off-by from its committer.
Sorry about that, I did take care of this in my local tree, but
apparently accidentally got rid of it in another rebase.
Will send v3 right away.
> ----------------------------------------------------------------------
>
> I think it's faster if you can test the commits yourself before sending
> the pull request. I'm using Stephen's scripts but I don't remember
> anymore where I got them. But Greg has his script available and I assume
> they test the same stuff:
>
> https://github.com/gregkh/gregkh-linux/tree/master/work
I tried using those scripts, but they didn't work on my machine for some
reason and I didn't have time to investigate yet. I'll try to make some
time for it soon.
- Felix
prev parent reply other threads:[~2021-06-19 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 17:33 pull request: mt76 2021-06-18 v2 Felix Fietkau
2021-06-19 6:49 ` Kalle Valo
2021-06-19 7:28 ` Felix Fietkau [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=aa6b2a81-4e52-4a5f-4253-8a54470e5270@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.