linux-i3c.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-i3c@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Rajeev Huralikoppi <rajeev.huralikoppi@silvaco.com>,
	Conor Culhane <conor.culhane@silvaco.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH v5 0/6] Silvaco I3C master driver
Date: Sat,  6 Feb 2021 00:44:29 +0100	[thread overview]
Message-ID: <161256866173.4836.10256863699232447925.b4-ty@bootlin.com> (raw)
In-Reply-To: <20210121101808.14654-1-miquel.raynal@bootlin.com>

On Thu, 21 Jan 2021 11:18:02 +0100, Miquel Raynal wrote:
> Here is the addition of a driver for the Silvaco I3C master IP.
> 
> Changes in v5:
> * Added Rob's R-by when relevant.
> * Fixed the robots warnings by pushing a little bit forward the changes in the
>   mipi-hci binding file.
> * Fixed the I3C master node name regex.
> * Removed the redundant $ref: entries when the hz suffix is used.
> * Simplified a little bit the regexes defining the child nodes.
> * Updated the reg propertie description to better describe each entry.
> 
> [...]

Applied, thanks!

[1/6] dt-bindings: i3c: Convert the bus description to yaml
      commit: 5e4cdca887fdb445f962b3dbc2a2514d7c025d9b
[2/6] dt-bindings: i3c: mipi-hci: Include the bus binding
      commit: de67276e66fcfcd404516eebfd6436239dd9882a
[3/6] dt-bindings: Add vendor prefix for Silvaco
      commit: 57f7c9ff1b3fdc2cccb377207e538bf5f3ab03cf
[4/6] dt-bindings: i3c: Describe Silvaco master binding
      commit: b8b0446f1f1afd58e5a9ba14ab2caa08797f3bb5
[5/6] i3c: master: svc: Add Silvaco I3C master driver
      commit: dd3c52846d5954acd43f0e771689302f27dadc28
[6/6] MAINTAINERS: Add Silvaco I3C master
      commit: f06a1af8e739cb573b79cd175fd88534e912bea0

Best regards,
-- 
Alexandre Belloni <alexandre.belloni@bootlin.com>

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

      parent reply	other threads:[~2021-02-05 23:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 10:18 [PATCH v5 0/6] Silvaco I3C master driver Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 1/6] dt-bindings: i3c: Convert the bus description to yaml Miquel Raynal
2021-02-05 21:31   ` Rob Herring
2021-01-21 10:18 ` [PATCH v5 2/6] dt-bindings: i3c: mipi-hci: Include the bus binding Miquel Raynal
2021-02-05 21:31   ` Rob Herring
2021-01-21 10:18 ` [PATCH v5 3/6] dt-bindings: Add vendor prefix for Silvaco Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 4/6] dt-bindings: i3c: Describe Silvaco master binding Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 5/6] i3c: master: svc: Add Silvaco I3C master driver Miquel Raynal
2021-01-21 10:18 ` [PATCH v5 6/6] MAINTAINERS: Add Silvaco I3C master Miquel Raynal
2021-02-05 23:44 ` 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=161256866173.4836.10256863699232447925.b4-ty@bootlin.com \
    --to=alexandre.belloni@bootlin.com \
    --cc=conor.culhane@silvaco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=nico@fluxnic.net \
    --cc=rajeev.huralikoppi@silvaco.com \
    --cc=robh+dt@kernel.org \
    --cc=thomas.petazzoni@bootlin.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).