public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: alexandre.belloni@bootlin.com, miquel.raynal@bootlin.com
Cc: arnd@arndb.de, bbrezillon@kernel.org,
	boris.brezillon@collabora.com, conor.culhane@silvaco.com,
	gregkh@linuxfoundation.org, imx@lists.linux.dev,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	pthombar@cadence.com
Subject: Re: [PATCH v2 1/1] MAINTAINERS: I3C: Add Frank Li as nxp I3C controller driver maintainer
Date: Thu, 26 Sep 2024 12:56:57 -0400	[thread overview]
Message-ID: <ZvWSWepBxc9wluw9@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <Zt9VDJ546znNR7AT@lizhi-Precision-Tower-5810>

On Mon, Sep 09, 2024 at 04:05:32PM -0400, Frank Li wrote:
> On Thu, Aug 15, 2024 at 10:16:09AM -0400, Frank Li wrote:
> > Add Frank Li as NXP i3c controller driver as maintainer and add mail list
> > imx@lists.linux.dev for it.
> >
> > Add Frank Li as I3C subsystem reviewer.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
>
> Miquel:
> 	Any comments?
>
> Frank

Alex:
	Almost one month passed, how make this go forward?

Frank

>
> > Change from v1 to v2
> > - Added to exist item
> >
> > Recently, I submit many i3c related patches and become familiar with i3c
> > protocol. So add me as svc-i3c-master.c maintainer.
> >
> > I reviewed other i3c patches. So add me as i3c subsystem reviewer.
> > ---
> >  MAINTAINERS | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 2b96899a78890..077e37eb018ce 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -10708,6 +10708,7 @@ F:	drivers/i3c/master/dw*
> >
> >  I3C SUBSYSTEM
> >  M:	Alexandre Belloni <alexandre.belloni@bootlin.com>
> > +R:	Frank Li <Frank.Li@nxp.com>
> >  L:	linux-i3c@lists.infradead.org (moderated for non-subscribers)
> >  S:	Maintained
> >  C:	irc://chat.freenode.net/linux-i3c
> > @@ -20961,8 +20962,10 @@ F:	drivers/video/fbdev/sm712*
> >
> >  SILVACO I3C DUAL-ROLE MASTER
> >  M:	Miquel Raynal <miquel.raynal@bootlin.com>
> > +M:	Frank Li <Frank.Li@nxp.com>
> >  M:	Conor Culhane <conor.culhane@silvaco.com>
> >  L:	linux-i3c@lists.infradead.org (moderated for non-subscribers)
> > +L:	imx@lists.linux.dev
> >  S:	Maintained
> >  F:	Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
> >  F:	drivers/i3c/master/svc-i3c-master.c
> > --
> > 2.34.1
> >

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

  reply	other threads:[~2024-09-26 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 14:16 [PATCH v2 1/1] MAINTAINERS: I3C: Add Frank Li as nxp I3C controller driver maintainer Frank Li
2024-09-09 20:05 ` Frank Li
2024-09-26 16:56   ` Frank Li [this message]
2024-09-30 16:22   ` Miquel Raynal
2024-09-30 17:08     ` Frank Li
2024-10-01 10:10       ` Miquel Raynal
2024-10-01 12:50         ` Frank Li
2025-02-20 22:22 ` 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=ZvWSWepBxc9wluw9@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=bbrezillon@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=conor.culhane@silvaco.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pthombar@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