From: "André Draszik" <andre.draszik@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
peter.griffin@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
tudor.ambarus@linaro.org, willmcvicker@google.com,
semen.protsenko@linaro.org, alim.akhtar@samsung.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos: gs101: add stable i2c aliases for gs101-oriole
Date: Mon, 12 Feb 2024 11:30:50 +0000 [thread overview]
Message-ID: <c16c1f18a8c6f33a608618d4ccf7d8c8dbb6f88b.camel@linaro.org> (raw)
In-Reply-To: <dce39e15-32a8-482c-8751-af4a133f82d2@linaro.org>
On Mon, 2024-02-12 at 12:18 +0100, Krzysztof Kozlowski wrote:
> I can drop it, but the actual problem is that what if downstream keeps
> changing aliases? They can do it...
We won't care at that stage, downstream should have no reason to divert from
upstream for numbering at some point in the future.
> The aliases are not there to match
> with downstream, but to have stable interface matching SCHEMATICS.
Except the schematics don't refer to the i2c busses by number.
Cheers,
Andre'
next prev parent reply other threads:[~2024-02-12 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 23:37 [PATCH] arm64: dts: exynos: gs101: add stable i2c aliases for gs101-oriole André Draszik
2024-01-31 20:40 ` William McVicker
2024-02-08 8:08 ` Krzysztof Kozlowski
2024-02-12 10:17 ` André Draszik
2024-02-12 11:18 ` Krzysztof Kozlowski
2024-02-12 11:30 ` André Draszik [this message]
2024-02-12 11:40 ` Krzysztof Kozlowski
2024-02-12 11:52 ` André Draszik
2024-02-12 12:07 ` Krzysztof Kozlowski
2024-02-12 12:38 ` André Draszik
2024-02-12 13:20 ` Krzysztof Kozlowski
2024-02-12 13:22 ` Krzysztof Kozlowski
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=c16c1f18a8c6f33a608618d4ccf7d8c8dbb6f88b.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@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).