From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] arm64: dts: renesas: falcon: Add I2C EEPROMs and sub-boards
Date: Fri, 5 Mar 2021 15:19:27 +0100 [thread overview]
Message-ID: <20210305141927.GC1312@kunai> (raw)
In-Reply-To: <CAMuHMdW8hqVPTcZcCFAHFUNOe63Ww_5wscLvRM3nms9Q4tS7Ww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
> > One minor question is: why do the labels in patches 2+3 have the "-id"
> > suffix and patch 1 does not? Don't we want consistency here?
>
> The EEPROMs on the sub-boards are labeled "Board ID" in the
> schematics, the EEPROMs on the CPU and BreakOut board aren't.
OK, super fine with me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-03-05 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 15:32 [PATCH v2 0/3] arm64: dts: renesas: falcon: Add I2C EEPROMs and sub-boards Geert Uytterhoeven
2021-03-04 15:32 ` [PATCH v2 1/3] arm64: dts: renesas: falcon: Add I2C EEPROM nodes Geert Uytterhoeven
2021-03-04 15:32 ` [PATCH v2 2/3] arm64: dts: renesas: falcon: Add CSI/DSI sub-board Geert Uytterhoeven
2021-03-04 15:32 ` [PATCH v2 3/3] arm64: dts: renesas: falcon: Add Ethernet sub-board Geert Uytterhoeven
2021-03-05 14:15 ` [PATCH v2 0/3] arm64: dts: renesas: falcon: Add I2C EEPROMs and sub-boards Wolfram Sang
2021-03-05 14:18 ` Geert Uytterhoeven
2021-03-05 14:19 ` Wolfram Sang [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=20210305141927.GC1312@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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).