From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Joel Stanley <joel@jms.id.au>
Cc: linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-aspeed@lists.ozlabs.org,
Matt Johnston <matt@codeconstruct.com.au>,
Vitor Soares <ivitro@gmail.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jack Chen <zenghuchen@google.com>,
Billy Tsai <billy_tsai@aspeedtech.com>,
Dylan Hung <dylan_hung@aspeedtech.com>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH v3 0/3] i3c dw,ast2600: Add a driver for the AST2600 i3c controller
Date: Wed, 05 Apr 2023 12:34:45 +0800 [thread overview]
Message-ID: <94e941a2895bbb40d7b87acd7de6525b8596b096.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CACPK8XdLpg2H4a2nHo4PokfBc4r3D8MbK2-62jXkPXAq8Q03Rg@mail.gmail.com>
Hi Joel,
> Given we have acks on the bindings, I think it's safe to send the
> device tree changes now so we can merge what you have in the upcoming
> merge window. If there's changes we can modify or revert.
OK, I'll get those into shape.
There is one dependency on this though, and unfortunately it requires
solving *two* of the known-hard problems in computer science:
Do we start at i3c0 or i3c1?
[i3c1 would match the schematic...]
Cheers,
Jeremy
next prev parent reply other threads:[~2023-04-05 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 9:14 [PATCH v3 0/3] i3c dw,ast2600: Add a driver for the AST2600 i3c controller Jeremy Kerr
2023-03-31 9:14 ` [PATCH v3 1/3] i3c: dw: Add infrastructure for platform-specific implementations Jeremy Kerr
2023-03-31 9:15 ` [PATCH v3 2/3] dt-bindings: i3c: Add AST2600 i3c controller Jeremy Kerr
2023-03-31 9:15 ` [PATCH v3 3/3] i3c: ast2600: Add AST2600 platform-specific driver Jeremy Kerr
[not found] ` <671a4bc0-526e-5224-7cb9-f80ebab2c0ef@linux.intel.com>
2023-04-27 23:58 ` Jeremy Kerr
2023-04-05 1:52 ` [PATCH v3 0/3] i3c dw,ast2600: Add a driver for the AST2600 i3c controller Joel Stanley
2023-04-05 4:34 ` Jeremy Kerr [this message]
2023-04-05 4:56 ` Joel Stanley
2023-04-05 5:15 ` Andrew Jeffery
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=94e941a2895bbb40d7b87acd7de6525b8596b096.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@aj.id.au \
--cc=billy_tsai@aspeedtech.com \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=ivitro@gmail.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i3c@lists.infradead.org \
--cc=matt@codeconstruct.com.au \
--cc=robh+dt@kernel.org \
--cc=zenghuchen@google.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).