From: Ninad Palsule <ninad@linux.ibm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: aspeed: Align GPIO hog name with bindings
Date: Thu, 16 Jan 2025 08:30:12 -0600 [thread overview]
Message-ID: <ae14daf4-c7fe-4fcc-89cd-5d1d8b320193@linux.ibm.com> (raw)
In-Reply-To: <cba3c5e0-624b-40a2-8b52-8d07604676a1@linux.ibm.com>
On 1/16/25 08:18, Ninad Palsule wrote:
>
> On 1/16/25 03:00, Krzysztof Kozlowski wrote:
>> Bindings expect GPIO hog names to end with 'hog' suffix, so correct it
>> to fix dtbs_check warnings like:
>>
>> aspeed-bmc-lenovo-hr630.dtb: pin_gpio_b5: $nodename:0:
>> 'pin_gpio_b5' does not match '^.+-hog(-[0-9]+)?$'
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>> .../dts/aspeed/aspeed-bmc-ampere-mtjade.dts | 2 +-
>> .../aspeed-bmc-arm-stardragon4800-rep2.dts | 4 +-
>> .../aspeed/aspeed-bmc-asrock-e3c246d4i.dts | 2 +-
>> .../dts/aspeed/aspeed-bmc-bytedance-g220a.dts | 4 +-
>> .../dts/aspeed/aspeed-bmc-delta-ahe50dc.dts | 2 +-
>> .../dts/aspeed/aspeed-bmc-ibm-bonnell.dts | 2 +-
>> .../dts/aspeed/aspeed-bmc-ibm-everest.dts | 2 +-
>> .../dts/aspeed/aspeed-bmc-ibm-rainier.dts | 4 +-
>> .../dts/aspeed/aspeed-bmc-lenovo-hr630.dts | 46 ++++++-------
>> .../dts/aspeed/aspeed-bmc-lenovo-hr855xg2.dts | 68 +++++++++----------
>> .../dts/aspeed/aspeed-bmc-opp-lanyang.dts | 14 ++--
>> .../boot/dts/aspeed/aspeed-bmc-opp-nicole.dts | 10 +--
>> .../dts/aspeed/aspeed-bmc-opp-palmetto.dts | 40 +++++------
>> .../dts/aspeed/aspeed-bmc-opp-romulus.dts | 6 +-
>> .../boot/dts/aspeed/aspeed-bmc-opp-zaius.dts | 8 +--
>> 15 files changed, 107 insertions(+), 107 deletions(-)
>>
Reviewed-by: Ninad Palsule <ninad@linux.ibm.com>
next prev parent reply other threads:[~2025-01-16 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 9:00 Krzysztof Kozlowski
2025-01-16 14:18 ` Ninad Palsule
2025-01-16 14:27 ` Krzysztof Kozlowski
2025-01-16 14:30 ` Ninad Palsule [this message]
2025-02-04 23:54 ` Andrew Jeffery
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=ae14daf4-c7fe-4fcc-89cd-5d1d8b320193@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®