From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: alexandre.belloni@bootlin.com, conor.culhane@silvaco.com,
imx@lists.linux.dev, joe@perches.com,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
zbigniew.lukwinski@linux.intel.com
Subject: Re: [PATCH v4 5/6] i3c: master: svc return actual transfer data len
Date: Thu, 30 Nov 2023 11:09:48 +0100 [thread overview]
Message-ID: <20231130110948.11a1ac71@xps-13> (raw)
In-Reply-To: <20231129221225.387952-6-Frank.Li@nxp.com>
Hi Frank,
Frank.Li@nxp.com wrote on Wed, 29 Nov 2023 17:12:24 -0500:
> I3C allow devices early terminate data transfer. So set "actual_len" to
> indicate how much data get by i3c_priv_xfer.
The title prefix should be the same in the two patches addressing the
SVC driver.
With this fixed:
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2023-11-30 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:12 [PATCH v4 0/6] i3c: master: some improvment for i3c master Frank Li
2023-11-29 22:12 ` [PATCH v4 1/6] i3c: master: add enable(disable) hot join in sys entry Frank Li
2023-11-30 10:13 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 2/6] i3c: master: svc: add hot join support Frank Li
2023-11-30 10:16 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 3/6] i3c: add actual_len in i3c_priv_xfer Frank Li
2023-11-30 10:17 ` Miquel Raynal
2023-11-29 22:12 ` [PATCH v4 4/6] i3c: svc: rename read_len as actual_len Frank Li
2023-11-29 22:12 ` [PATCH v4 5/6] i3c: master: svc return actual transfer data len Frank Li
2023-11-30 10:09 ` Miquel Raynal [this message]
2023-11-29 22:12 ` [PATCH v4 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2023-11-30 10:19 ` Miquel Raynal
2023-11-30 17:49 ` Frank Li
2023-11-30 19:16 ` Miquel Raynal
2023-11-30 22:00 ` [PATCH v4 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device statusy Frank Li
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=20231130110948.11a1ac71@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=imx@lists.linux.dev \
--cc=joe@perches.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbigniew.lukwinski@linux.intel.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