From: Kalle Valo <kvalo@codeaurora.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-Hsien Lin <chi-hsien.lin@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH 5.12 regression fix resend 0/1] brcmfmac: p2p: Fix recently introduced deadlock issue
Date: Tue, 06 Apr 2021 13:24:44 +0300 [thread overview]
Message-ID: <87im4zoglv.fsf@codeaurora.org> (raw)
In-Reply-To: <20210405205429.19304-1-hdegoede@redhat.com> (Hans de Goede's message of "Mon, 5 Apr 2021 22:54:28 +0200")
Hans de Goede <hdegoede@redhat.com> writes:
> Hi,
>
> Here is a resend of a regression/deadlock fix for 5.12 which I send out
> around rc1 but which still is not in Linus' tree.
>
> This is quite a bad bug, breaking things for most broadcom wifi users.
>
> Can we get this regression fix on its way to Linus for 5.12-rc7 ASAP
> please ?
The patch has been already applied but I have not yet sent a pull
request, the plan is to send it later this week.
Please don't resend patches which have been already applied, that
creates more work for me.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-04-06 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 20:54 [PATCH 5.12 regression fix resend 0/1] brcmfmac: p2p: Fix recently introduced deadlock issue Hans de Goede
2021-04-05 20:54 ` [PATCH 5.12 regression fix resend 1/1] " Hans de Goede
2021-04-06 10:17 ` Kalle Valo
[not found] ` <20210406101705.38F85C43463@smtp.codeaurora.org>
2021-04-06 10:29 ` Hans de Goede
2021-04-06 10:24 ` 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=87im4zoglv.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=johannes.berg@intel.com \
--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 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).