From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Frank Li <Frank.li@nxp.com>
Cc: miquel.raynal@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: (subset) [v5 resend 0/6] i3c: master: some improvment for i3c master
Date: Tue, 9 Jan 2024 08:35:07 +0100 [thread overview]
Message-ID: <2024010907350708773e04@mail.local> (raw)
In-Reply-To: <ZZyfL/wWSW1oMOec@lizhi-Precision-Tower-5810>
On 08/01/2024 20:19:43-0500, Frank Li wrote:
> On Mon, Jan 08, 2024 at 01:03:50AM +0100, Alexandre Belloni wrote:
> >
> > On Fri, 01 Dec 2023 17:25:26 -0500, Frank Li wrote:
> > > There are three major improvement
> > >
> > > 1. Add actual size in i3c_transfer because i3c allow target early termiate
> > > transfer.
> > > 2. Add API for i3c_dev_gettstatus_format1 for i3c comand GET_STATUS.
> > > 3. svc master support hotjoin
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/6] i3c: master: add enable(disable) hot join in sys entry
> > commit: 317bacf960a4879af22d12175f47d284930b3273
> > [2/6] i3c: master: svc: add hot join support
> > commit: 05b26c31a4859af9e75b7de77458e99358364fe1
> > [3/6] i3c: add actual_len in i3c_priv_xfer
> > commit: e5e3df06ac98d15cfb10bb5c12356709365e91b2
> > [4/6] i3c: master: svc: rename read_len as actual_len
> > commit: 6fb61734a74eaa307a5b6a0bee770e736d8acf89
> > [5/6] i3c: master: svc: return actual transfer data len
> > commit: 6d1a19d34e2cc07ca9cdad8892da94e716e9d15f
>
> Why not pckup 6/6:
> i3c: add API i3c_dev_gettstatus_format1() to get target device status
>
As it was discussed, it doesn't have any users.
> Frank
>
> >
> > Best regards,
> >
> > --
> > Alexandre Belloni, co-owner and COO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2024-01-09 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 22:25 [v5 resend 0/6] i3c: master: some improvment for i3c master Frank Li
2023-12-01 22:25 ` [v5 resend 1/6] i3c: master: add enable(disable) hot join in sys entry Frank Li
2023-12-01 22:25 ` [v5 resend 2/6] i3c: master: svc: add hot join support Frank Li
2023-12-01 22:25 ` [v5 resend 3/6] i3c: add actual_len in i3c_priv_xfer Frank Li
2023-12-20 1:51 ` Joshua Yeong
2023-12-20 1:55 ` Joshua Yeong
2023-12-20 20:55 ` Frank Li
2023-12-01 22:25 ` [v5 resend 4/6] i3c: master: svc: rename read_len as actual_len Frank Li
2023-12-01 22:25 ` [v5 resend 5/6] i3c: master: svc: return actual transfer data len Frank Li
2023-12-01 22:25 ` [v5 resend 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2023-12-19 16:29 ` [v5 resend 0/6] i3c: master: some improvment for i3c master Frank Li
2024-01-08 0:03 ` (subset) " Alexandre Belloni
2024-01-09 1:19 ` Frank Li
2024-01-09 7:35 ` Alexandre Belloni [this message]
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=2024010907350708773e04@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Frank.li@nxp.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=miquel.raynal@bootlin.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).