From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Tim Harvey <tharvey@gateworks.com>,
Michael Walle <mwalle@kernel.org>, Lee Jones <lee@kernel.org>,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: Mathew McBride <matt@traverse.com.au>
Subject: Re: [PATCH] dt-bindings: mfd: Move embedded controllers to own directory
Date: Thu, 21 Aug 2025 11:57:59 +0200 [thread overview]
Message-ID: <7d2bea94-b6a0-49c2-bd83-e5421a6ce567@linaro.org> (raw)
In-Reply-To: <20250821062840.9383-2-krzysztof.kozlowski@linaro.org>
On 21/08/2025 08:28, Krzysztof Kozlowski wrote:
> Move ChromeOS Embedded Controller, Gateworks System Controller and
> Kontron sl28cpld Board Management Controller to new subdirectory
> "embedded-controller" matching their purpose. MFD is coming from Linux
> and does not really fit the actual purpose of this hardware.
>
> Rename Gateworks GSC filename to match compatible, as preferred for
> bindings.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> Cc: Mathew McBride <matt@traverse.com.au>
>
> Lee,
> Can you take it via MFD?
> ---
> .../bindings/{mfd => embedded-controller}/google,cros-ec.yaml | 2 +-
> .../gateworks-gsc.yaml => embedded-controller/gw,gsc.yaml} | 2 +-
> .../{mfd => embedded-controller}/kontron,sl28cpld.yaml | 2 +-
I forgot to update references in other files (except maintainers). This
needs v2.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-21 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 6:28 Krzysztof Kozlowski
2025-08-21 6:37 ` Michael Walle
2025-08-21 9:57 ` Krzysztof Kozlowski [this message]
2025-08-21 13:24 ` Rob Herring (Arm)
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=7d2bea94-b6a0-49c2-bd83-e5421a6ce567@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@traverse.com.au \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=tharvey@gateworks.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
all inboxes | Powered by JetHome®