From: Krzysztof Kozlowski <krzk@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Artem Novak <artem122novak@gmail.com>,
robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: document Casio fx-9750GIII
Date: Thu, 22 Oct 2026 09:57:58 +0200 [thread overview]
Message-ID: <643ce64e-23d4-4de3-b7c8-8e1e9b268d03@kernel.org> (raw)
In-Reply-To: <4f37ee0df5c5b0b29c69b3770c06a885f0562c74.camel@physik.fu-berlin.de>
On 22/10/2026 09:46, John Paul Adrian Glaubitz wrote:
> On Thu, 2026-10-22 at 09:33 +0200, Krzysztof Kozlowski wrote:
>>> There is a Casio calculator community out there that are users
>>> for this.
>>
>> Upstream user, so any known upstream open source project using Linux
>> kernel DT bindings. We do not need bindings for non-upstream users.
>
> Yes, I realized that hadn't had any coffee yet and I misunderstood
> that comment.
>
> I think that Artem is sending the users for these bindings in a different
> patch set. I have not been able to review the changes for arch/sh yet.
So this looks like binding for the board/soc, thus must be sent along
with the DTS patchset.
See:
https://lore.kernel.org/all/20231121-topic-sm8650-upstream-dt-v3-0-db9d0507ffd3@linaro.org/
https://lore.kernel.org/linux-samsung-soc/CADrjBPq_0nUYRABKpskRF_dhHu+4K=duPVZX==0pr+cjSL_caQ@mail.gmail.com/T/#m2d9130a1342ab201ab49670fa6c858ee3724c83c
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-22 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 6:39 [PATCH] dt-bindings: soc: document Casio fx-9750GIII Artem Novak
2026-10-22 7:16 ` Krzysztof Kozlowski
2026-10-22 7:27 ` John Paul Adrian Glaubitz
2026-10-22 7:33 ` Krzysztof Kozlowski
2026-10-22 7:46 ` John Paul Adrian Glaubitz
2026-10-22 7:57 ` Krzysztof Kozlowski [this message]
2026-10-22 8:05 ` Artem Novak
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=643ce64e-23d4-4de3-b7c8-8e1e9b268d03@kernel.org \
--to=krzk@kernel.org \
--cc=artem122novak@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=krzk+dt@kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=robh@kernel.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