From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Frank Li" <Frank.Li@nxp.com>,
linux-i3c@lists.infradead.org,
"Przemysław Gaj" <pgaj@cadence.com>
Subject: [PATCH v3 0/3] i3c: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP
Date: Sat, 28 Jun 2025 21:20:27 +0200 [thread overview]
Message-ID: <20250628192027.3932-5-wsa+renesas@sang-engineering.com> (raw)
Changes since v2:
* updated commit message again
This checkpatch warning makes sense here: "ENOTSUPP is not a SUSV4 error
code, prefer EOPNOTSUPP" We don't have a userspace interface yet, but we
probably will get one. So, let's convert these error codes now, before
it will be forgotten in the future, and they could slip through to
applications.
This is based on 6.16-rc3 plus "[PATCH] i3c: don't fail if GETHDRCAP is
unsupported" which I sent earlier. During its development, the issue
became apparent. Automatically generated and build tested only.
Looking forward to comments.
Wolfram Sang (3):
i3c: master: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP
i3c: dw: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP
i3c: master: cdns: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP
drivers/i3c/master.c | 20 ++++++++++----------
drivers/i3c/master/dw-i3c-master.c | 8 ++++----
drivers/i3c/master/i3c-master-cdns.c | 12 ++++++------
3 files changed, 20 insertions(+), 20 deletions(-)
--
2.47.2
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2025-06-28 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 19:20 Wolfram Sang [this message]
2025-06-28 19:20 ` [PATCH v3 1/3] i3c: master: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP Wolfram Sang
2025-06-30 15:12 ` Frank Li
2025-06-28 19:20 ` [PATCH v3 2/3] i3c: dw: " Wolfram Sang
2025-06-30 15:13 ` Frank Li
2025-06-28 19:20 ` [PATCH v3 3/3] i3c: master: cdns: " Wolfram Sang
2025-06-30 15:13 ` Frank Li
2025-07-07 21:33 ` [PATCH v3 0/3] i3c: " Alexandre Belloni
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=20250628192027.3932-5-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=pgaj@cadence.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;
as well as URLs for NNTP newsgroup(s).