From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org,
Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Michael Walle <mwalle@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>,
"Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] spi: Fix error code checking in spi_mem_exec_op()
Date: Fri, 15 Mar 2024 17:13:13 +0000 [thread overview]
Message-ID: <171052279309.52555.176747967230384513.b4-ty@kernel.org> (raw)
In-Reply-To: <20240313194530.3150446-1-florian.fainelli@broadcom.com>
On Wed, 13 Mar 2024 12:45:30 -0700, Florian Fainelli wrote:
> After commit cff49d58f57e ("spi: Unify error codes by replacing -ENOTSUPP with
> -EOPNOTSUPP"), our SPI NOR flashes would stop probing with the following
> visible in the kernel log:
>
> [ 2.196300] brcmstb_qspi f0440920.qspi: using bspi-mspi mode
> [ 2.210295] spi-nor: probe of spi1.0 failed with error -95
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Fix error code checking in spi_mem_exec_op()
commit: 29895ce18311ddd702973ddb3a6c687db663e0fb
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
prev parent reply other threads:[~2024-03-15 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 19:45 [PATCH v2] spi: Fix error code checking in spi_mem_exec_op() Florian Fainelli
2024-03-14 5:41 ` Mika Westerberg
2024-03-14 7:05 ` Tudor Ambarus
2024-03-14 7:07 ` Miquel Raynal
2024-03-15 17:13 ` Mark Brown [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=171052279309.52555.176747967230384513.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@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 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.