From: Kalle Valo <kvalo@codeaurora.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: Markus Theil <markus.theil@tu-ilmenau.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mt76: fix fix ampdu locking
Date: Thu, 21 Nov 2019 06:53:18 +0000 [thread overview]
Message-ID: <0101016e8cbc907e-e065156e-ccc2-46bd-8e51-45a1494ce723-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <9413ca21-94c3-857b-1156-e4a949acf390@nbd.name> (Felix Fietkau's message of "Wed, 20 Nov 2019 21:14:07 +0100")
Felix Fietkau <nbd@nbd.name> writes:
> On 2019-11-20 21:05, Markus Theil wrote:
>> The current ampdu locking code does not unlock its mutex in the early
>> return case. This patch fixes it.
>>
>> Signed-off-by: Markus Theil <markus.theil@tu-ilmenau.de>
>
> Acked-by: Felix Fietkau <nbd@nbd.name>
>
> Kalle, I think this should go on top of my pull request quickly, since
> it fixes a regression in a commit from that pull request (introduced via
> rebase on top of Johannes' last change of that code).
> Do you want me to send another pull request with just this patch, or can
> you take it directly?
A lot easier to take it directly, so let's do that. I now assigned this
patch to me on patchwork and I'll try to remember apply it later today.
> In the latter case, feel free to also remove one of the two "fix"
> words in the subject :)
Ok, will fix (no pun intended ;)
--
Kalle Valo
next prev parent reply other threads:[~2019-11-21 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 20:05 [PATCH] mt76: fix fix ampdu locking Markus Theil
2019-11-20 20:14 ` Felix Fietkau
2019-11-20 20:32 ` Markus Theil
2019-11-21 6:53 ` Kalle Valo [this message]
2019-11-21 18:34 ` [PATCH] mt76: " Kalle Valo
2019-11-21 18:36 ` Kalle Valo
2019-11-21 18:43 ` [PATCH] mt76: fix " 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=0101016e8cbc907e-e065156e-ccc2-46bd-8e51-45a1494ce723-000000@us-west-2.amazonses.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=markus.theil@tu-ilmenau.de \
--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).