From: "wsa+renesas@sang-engineering.com" <wsa+renesas@sang-engineering.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Billy Tsai" <billy_tsai@aspeedtech.com>,
"pgaj@cadence.com" <pgaj@cadence.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"conor.culhane@silvaco.com" <conor.culhane@silvaco.com>,
"aniketmaurya@google.com" <aniketmaurya@google.com>,
"Shyam-sundar.S-k@amd.com" <Shyam-sundar.S-k@amd.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
"xiaopei01@kylinos.cn" <xiaopei01@kylinos.cn>,
"Guruvendra.Punugupati@amd.com" <Guruvendra.Punugupati@amd.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
BMC-SW <BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v2 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API
Date: Mon, 17 Feb 2025 10:57:37 +0100 [thread overview]
Message-ID: <Z7MIEWbrK9bGUr4d@ninjato> (raw)
In-Reply-To: <2025020416561726c9efa0@mail.local>
[-- Attachment #1.1: Type: text/plain, Size: 131 bytes --]
> I guess Wolfram will be the one have the preference, I'm fine using the
> existing API as-is.
Happy to take (tested) patches.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 111 bytes --]
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: "wsa+renesas@sang-engineering.com" <wsa+renesas@sang-engineering.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"Billy Tsai" <billy_tsai@aspeedtech.com>,
"pgaj@cadence.com" <pgaj@cadence.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"conor.culhane@silvaco.com" <conor.culhane@silvaco.com>,
"aniketmaurya@google.com" <aniketmaurya@google.com>,
"Shyam-sundar.S-k@amd.com" <Shyam-sundar.S-k@amd.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
"xiaopei01@kylinos.cn" <xiaopei01@kylinos.cn>,
"Guruvendra.Punugupati@amd.com" <Guruvendra.Punugupati@amd.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
BMC-SW <BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v2 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API
Date: Mon, 17 Feb 2025 10:57:37 +0100 [thread overview]
Message-ID: <Z7MIEWbrK9bGUr4d@ninjato> (raw)
In-Reply-To: <2025020416561726c9efa0@mail.local>
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
> I guess Wolfram will be the one have the preference, I'm fine using the
> existing API as-is.
Happy to take (tested) patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-19 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 9:17 [PATCH v2 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API Billy Tsai
2025-02-04 9:17 ` Billy Tsai
2025-02-04 9:17 ` [PATCH v2 2/2] i3c: mipi-i3c-hci: Use I2C DMA-safe api Billy Tsai
2025-02-04 9:17 ` Billy Tsai
2025-02-04 15:16 ` Mukesh Kumar Savaliya
2025-02-04 15:16 ` Mukesh Kumar Savaliya
2025-02-05 11:28 ` Jarkko Nikula
2025-02-05 11:28 ` Jarkko Nikula
2025-02-05 16:51 ` Frank Li
2025-02-05 16:51 ` Frank Li
2025-02-04 9:50 ` [PATCH v2 1/2] i3c: Remove the const qualifier from i2c_msg pointer in i2c_xfers API Thomas Weißschuh
2025-02-04 9:50 ` Thomas Weißschuh
2025-02-04 10:09 ` Billy Tsai
2025-02-04 10:09 ` Billy Tsai
2025-02-04 16:50 ` Thomas Weißschuh
2025-02-04 16:50 ` Thomas Weißschuh
2025-02-04 16:56 ` Alexandre Belloni
2025-02-04 16:56 ` Alexandre Belloni
2025-02-17 9:57 ` wsa+renesas [this message]
2025-02-17 9:57 ` wsa+renesas
2025-02-05 16:50 ` Frank Li
2025-02-05 16:50 ` Frank Li
2025-02-20 22:09 ` Alexandre Belloni
2025-02-20 22:09 ` 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=Z7MIEWbrK9bGUr4d@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=BMC-SW@aspeedtech.com \
--cc=Guruvendra.Punugupati@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aniketmaurya@google.com \
--cc=billy_tsai@aspeedtech.com \
--cc=conor.culhane@silvaco.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=miquel.raynal@bootlin.com \
--cc=pgaj@cadence.com \
--cc=xiaopei01@kylinos.cn \
/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.