From: Sasha Levin <sashal@kernel.org>
To: Luca Coelho <luca@coelho.fi>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v5.2 1/2] iwlwifi: mvm: add a wrapper around rs_tx_status to handle locks
Date: Fri, 11 Oct 2019 12:03:30 -0400 [thread overview]
Message-ID: <20191011160330.GC2635@sasha-vm> (raw)
In-Reply-To: <20191011061402.32107-1-luca@coelho.fi>
On Fri, Oct 11, 2019 at 09:14:01AM +0300, Luca Coelho wrote:
>From: Gregory Greenman <gregory.greenman@intel.com>
>
>[ Upstream commit 23babdf06779482a65c5072a145d826a62979534 ]
>
>iwl_mvm_rs_tx_status can be called from two places in the code, but the
>mutex is taken only on one of the calls. Split it into a wrapper taking
>locks and an internal __iwl_mvm_rs_tx_status function.
v5.2 is EOL, any other kernels this needs to be in?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-11 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 6:14 [PATCH v5.2 1/2] iwlwifi: mvm: add a wrapper around rs_tx_status to handle locks Luca Coelho
2019-10-11 6:14 ` [PATCH v5.2 2/2] iwlwifi: mvm: replace RS mutex with a spin_lock Luca Coelho
2019-10-11 16:03 ` Sasha Levin [this message]
2019-10-12 9:41 ` [PATCH v5.2 1/2] iwlwifi: mvm: add a wrapper around rs_tx_status to handle locks Luca Coelho
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=20191011160330.GC2635@sasha-vm \
--to=sashal@kernel.org \
--cc=luca@coelho.fi \
--cc=stable@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