public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Frank Li <Frank.li@nxp.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-i3c@lists.infradead.org
Subject: Re: [PATCH v2 1/3] i3c: master: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP
Date: Sat, 28 Jun 2025 21:15:27 +0200	[thread overview]
Message-ID: <aGA_TxSFb3shGmnO@shikoro> (raw)
In-Reply-To: <aGA2DCfUfK5ZN4bR@lizhi-Precision-Tower-5810>


> I understand this. But the sentence "we never want this(ENOTSUPP) to slip to
> userspace" literal means (I understand at least).
> 
> we don't expect to export it to userspace at all.
> 
> Actually your means "we don't know if it will skip to user space in future"

Sorry, I simply don't understand what you mean here. But I think it is
not worth the time to discuss this further anyhow. I will just use your
suggested commit message. It is not that important.


-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-06-28 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 11:17 [PATCH v2 0/3] i3c: replace ENOTSUPP with SUSV4-compliant EOPNOTSUPP Wolfram Sang
2025-06-27 11:17 ` [PATCH v2 1/3] i3c: master: " Wolfram Sang
2025-06-27 20:46   ` Frank Li
2025-06-28 10:12     ` Wolfram Sang
2025-06-28 18:59       ` Frank Li
2025-06-28 19:15         ` Wolfram Sang [this message]
2025-06-27 11:17 ` [PATCH v2 2/3] i3c: dw: " Wolfram Sang
2025-06-27 11:17 ` [PATCH v2 3/3] i3c: master: cdns: " Wolfram Sang

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=aGA_TxSFb3shGmnO@shikoro \
    --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 \
    /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