From: Mark Brown <broonie@kernel.org>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Michael Walle" <michael@walle.cc>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Dhruva Gole" <d-gole@ti.com>,
linux-mtd@lists.infradead.org,
"Kamal Dasu" <kamal.dasu@broadcom.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Mario Kicherer" <dev@kicherer.org>,
"Chuanhong Guo" <gch981213@gmail.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
"AceLan Kao" <acelan.kao@canonical.com>
Subject: Re: [PATCH v7 1/2] spi: Unify error codes by replacing -ENOTSUPP with -EOPNOTSUPP
Date: Thu, 30 Nov 2023 14:19:54 +0000 [thread overview]
Message-ID: <170135399481.77996.14013825490187287215.b4-ty@kernel.org> (raw)
In-Reply-To: <20231129064311.272422-1-acelan.kao@canonical.com>
On Wed, 29 Nov 2023 14:43:10 +0800, AceLan Kao wrote:
> This commit updates the SPI subsystem, particularly affecting "SPI MEM"
> drivers and core parts, by replacing the -ENOTSUPP error code with
> -EOPNOTSUPP.
>
> The key motivations for this change are as follows:
> 1. The spi-nor driver currently uses EOPNOTSUPP, whereas calls to spi-mem
> might return ENOTSUPP. This update aims to unify the error reporting
> within the SPI subsystem for clarity and consistency.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: Unify error codes by replacing -ENOTSUPP with -EOPNOTSUPP
commit: cff49d58f57e5667c10a0db85d7461790bb85cf8
[2/2] mtd: spi-nor: Stop reporting warning message when soft reset is not suported
commit: 7a030abc0185b30a3fd19a7431347c6f5a82c588
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:[~2023-11-30 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 6:43 AceLan Kao
2023-11-29 6:43 ` [PATCH v7 2/2] mtd: spi-nor: Stop reporting warning message when soft reset is not suported AceLan Kao
2023-11-29 7:46 ` Tudor Ambarus
2023-11-29 21:19 ` Mark Brown
2023-11-30 2:27 ` AceLan Kao
2023-11-30 9:20 ` Tudor Ambarus
2023-11-29 8:40 ` Miquel Raynal
2023-11-29 7:05 ` [PATCH v7 1/2] spi: Unify error codes by replacing -ENOTSUPP with -EOPNOTSUPP Mika Westerberg
2023-11-29 7:38 ` Tudor Ambarus
2023-11-29 8:28 ` Michael Walle
2023-11-29 8:39 ` Miquel Raynal
2023-11-30 14:19 ` Mark Brown [this message]
2024-03-13 15:40 ` Florian Fainelli
2024-03-13 15:56 ` Michael Walle
2024-03-13 17:13 ` Florian Fainelli
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=170135399481.77996.14013825490187287215.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=d-gole@ti.com \
--cc=dev@kicherer.org \
--cc=gch981213@gmail.com \
--cc=j.neuschaefer@gmx.net \
--cc=kamal.dasu@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®