From: Mark Brown <broonie@kernel.org>
To: alexandru.tachici@analog.com, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
nsaenz@kernel.org, f.fainelli@gmail.com, rjui@broadcom.com,
swarren@wwwdotorg.org, bcm-kernel-feedback-list@broadcom.com,
bootc@bootc.net, nuno.sa@analog.com
Subject: Re: [PATCH 0/1] spi: spi-bcm2835: Fix deadlock
Date: Tue, 20 Jul 2021 19:48:16 +0100 [thread overview]
Message-ID: <162680680557.11423.14003826010912823109.b4-ty@kernel.org> (raw)
In-Reply-To: <20210716210245.13240-1-alexandru.tachici@analog.com>
On Sat, 17 Jul 2021 00:02:44 +0300, alexandru.tachici@analog.com wrote:
> The bcm2835_spi_transfer_one function can create a deadlock
> if it is called while another thread already has the
> CCF lock.
>
> This behavior was observed at boot and when trying to
> print the clk_summary debugfs. I had registered
> at the time multiple clocks of AD9545 through the CCF.
> Tested this using an RPi 4 connected to AD9545 through SPI.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-bcm2835: Fix deadlock
commit: c45c1e82bba130db4f19d9dbc1deefcf4ea994ed
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
next prev parent reply other threads:[~2021-07-20 18:49 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 ` [PATCH 0/1] " Mark Brown
2021-07-20 18:48 ` Mark Brown [this message]
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=162680680557.11423.14003826010912823109.b4-ty@kernel.org \
--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.