From: Jeremy Kerr <jk@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] ARM: dts: aspeed-g6: Add nodes for i3c controllers
Date: Thu, 02 May 2024 19:10:19 +0800 [thread overview]
Message-ID: <f14b79f4771a4216be6eb2de4352f9f1dda0eafc.camel@codeconstruct.com.au> (raw)
In-Reply-To: <c5331cf8-7295-4e6a-ba39-e0751a2c357e@kernel.org>
Hi Krysztof,
> Your first node is empty and that is not readable.
I'd argue that separating the i3c definitions makes the source more
readable (granted, at the cognitive expense of having to dereference a
label), but ok.
I'll send a v2 with the bus definitions inline, but first reworking the
existing i2c definitions to use the same format.
Cheers,
Jeremy
prev parent reply other threads:[~2024-05-02 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 3:38 [PATCH] ARM: dts: aspeed-g6: Add nodes for i3c controllers Jeremy Kerr
2024-05-01 10:24 ` Krzysztof Kozlowski
2024-05-01 11:17 ` Jeremy Kerr
2024-05-01 16:45 ` Krzysztof Kozlowski
2024-05-02 11:10 ` Jeremy Kerr [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=f14b79f4771a4216be6eb2de4352f9f1dda0eafc.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=linux-aspeed@lists.ozlabs.org \
/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).