linux-i3c.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.li@nxp.com>
Cc: alexandre.belloni@bootlin.com, 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: Mon, 30 Sep 2024 18:22:35 +0200	[thread overview]
Message-ID: <20240930182235.52c4530e@xps-13> (raw)
In-Reply-To: <Zt9VDJ546znNR7AT@lizhi-Precision-Tower-5810>

Hi Frank,

Frank.li@nxp.com wrote on Mon, 9 Sep 2024 16:05:32 -0400:

> 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?

I guess we'll happily take your feedback on patches targeting the SVC
driver, you've been working a lot on it. However, in general there has
been a lot of discussions happening on your substantial patchsets and
little to no convergence in the end. I understand you want to push your
patches upstream and I also want to make things move forward, but maybe
one of the reasons for the stalls is the lack of fluent exchanges
between us and the difficulty to explain bigger pictures in a clear
way. I believe maintaining a subsystem still requires a bit more
experience on this regard.

Thanks,
Miquèl

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

  parent reply	other threads:[~2024-09-30 16:22 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
2024-09-30 16:22   ` Miquel Raynal [this message]
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=20240930182235.52c4530e@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=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=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;
as well as URLs for NNTP newsgroup(s).