From: Mark Brown <broonie@kernel.org>
To: alexandru.tachici@analog.com
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
nuno.sa@analog.com, bootc@bootc.net, swarren@wwwdotorg.org,
bcm-kernel-feedback-list@broadcom.com, rjui@broadcom.com,
f.fainelli@gmail.com, nsaenz@kernel.org
Subject: Re: [PATCH 0/1] spi: spi-bcm2835: Fix deadlock
Date: Tue, 20 Jul 2021 13:33:32 +0100 [thread overview]
Message-ID: <20210720123332.GA5042@sirena.org.uk> (raw)
In-Reply-To: <20210716210245.13240-1-alexandru.tachici@analog.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Sat, Jul 17, 2021 at 12:02:44AM +0300, alexandru.tachici@analog.com wrote:
> From: Alexandru Tachici <alexandru.tachici@analog.com>
>
> The bcm2835_spi_transfer_one function can create a deadlock
> if it is called while another thread already has the
> CCF lock.
Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff. This reduces mail volume and ensures that
any important information is recorded in the changelog rather than being
lost.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-20 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 21:02 [PATCH 0/1] spi: spi-bcm2835: Fix deadlock alexandru.tachici
2021-07-16 21:02 ` [PATCH 1/1] " alexandru.tachici
2021-07-19 23:50 ` Florian Fainelli
2021-07-20 12:33 ` Mark Brown [this message]
2021-07-20 18:48 ` [PATCH 0/1] " Mark Brown
2021-07-21 6:47 ` Sa, Nuno
2021-07-21 12:32 ` Mark Brown
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=20210720123332.GA5042@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandru.tachici@analog.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bootc@bootc.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nsaenz@kernel.org \
--cc=nuno.sa@analog.com \
--cc=rjui@broadcom.com \
--cc=swarren@wwwdotorg.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.