From: Mark Brown <broonie@kernel.org>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: "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-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] spi: Replace -ENOTSUPP with -EOPNOTSUPP in op checking
Date: Thu, 16 Nov 2023 15:21:01 +0000 [thread overview]
Message-ID: <401df72f-9255-4da3-b97e-93d3f38d352c@sirena.org.uk> (raw)
In-Reply-To: <20231116024338.337304-1-acelan.kao@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
On Thu, Nov 16, 2023 at 10:43:37AM +0800, AceLan Kao wrote:
> The purpose of this patch is to distinguish the "operation not support"
> error from the generic "not support", so that drivers could better
> handle different errors.
What is the intended distinction between the two?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-11-16 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 2:43 AceLan Kao
2023-11-16 2:43 ` [PATCH v6 2/2] mtd: spi-nor: Stop reporting warning message when soft reset is not suported AceLan Kao
2023-11-16 15:21 ` Mark Brown [this message]
2023-11-16 15:37 ` [PATCH v6 1/2] spi: Replace -ENOTSUPP with -EOPNOTSUPP in op checking Michael Walle
2023-11-17 9:32 ` Tudor Ambarus
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=401df72f-9255-4da3-b97e-93d3f38d352c@sirena.org.uk \
--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=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®