From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Tali Perry <tali.perry1@gmail.com>,
Patrick Venture <venture@google.com>,
Nancy Yuen <yuenn@google.com>,
Benjamin Fair <benjaminfair@google.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: nuvoton: Align GPIO hog name with bindings
Date: Thu, 13 Feb 2025 12:05:02 +1030 [thread overview]
Message-ID: <5d84475dc07c43fada8f3e10169739d57348eaa4.camel@codeconstruct.com.au> (raw)
In-Reply-To: <bdd7b203-ccb3-453b-ae91-32f257fc909f@kernel.org>
On Wed, 2025-02-12 at 21:36 +0100, Krzysztof Kozlowski wrote:
> On 16/01/2025 10:00, Krzysztof Kozlowski wrote:
> > Bindings expect GPIO hog names to end with 'hog' suffix, so correct
> > it
> > to fix dtbs_check warnings like:
> >
> > nuvoton-npcm750-runbmc-olympus.dtb: G1A_P0_0: $nodename:0:
> > 'G1A_P0_0' does not match '^.+-hog(-[0-9]+)?$'
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> > ---
> >
> > Changes in v2:
> > 1. Rename rest of the nodes I missed.
> > ---
> > .../boot/dts/nuvoton/nuvoton-npcm730-gbs.dts | 12 +-
> > .../nuvoton-npcm750-runbmc-olympus.dts | 120 +++++++++-----
> > ----
> > 2 files changed, 66 insertions(+), 66 deletions(-)
> >
>
> Any comments? Can this be merged?
Joel was taking NPCM SoC patches through the BMC tree. I'll pick this
up. We should probably update MAINTAINERS so they don't get lost.
Andrew
prev parent reply other threads:[~2025-02-13 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 9:00 Krzysztof Kozlowski
2025-02-12 20:36 ` Krzysztof Kozlowski
2025-02-13 1:35 ` Andrew Jeffery [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=5d84475dc07c43fada8f3e10169739d57348eaa4.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@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
all inboxes | Powered by JetHome®