From: Ninad Palsule <ninad@linux.ibm.com>
To: Rob Herring <robh@kernel.org>
Cc: andrew+netdev@lunn.ch, pabeni@redhat.com,
linux-arm-kernel@lists.infradead.org, edumazet@google.com,
joel@jms.id.au, krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
andrew@codeconstruct.com.au, devicetree@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org,
openipmi-developer@lists.sourceforge.net, netdev@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, conor+dt@kernel.org,
eajames@linux.ibm.com, minyard@acm.org
Subject: Re: [PATCH v5 03/10] dt-bindings: gpio: ast2400-gpio: Add hogs parsing
Date: Thu, 16 Jan 2025 14:37:38 -0600 [thread overview]
Message-ID: <c61740c8-8dd3-4d59-8553-1dea4cbd5c93@linux.ibm.com> (raw)
In-Reply-To: <CAL_JsqK1z4w62pGX0NgM7by+QRFcmBadw=CRVrvF2vv-zgAExg@mail.gmail.com>
Hi Rob,
>> I am not seeing any error even after upgrading dtschema. Also this mail
>> also doesn't show any warning. Is this false negative?
>
> I believe this happens when a prior patch in the series has an error.
Thanks for the response. I have sent a next version.
--
Thanks & Regards,
Ninad
next prev parent reply other threads:[~2025-01-16 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 22:01 [PATCH v5 00/10] DTS updates for system1 BMC Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 01/10] dt-bindings: net: faraday,ftgmac100: Add phys mode Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 02/10] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-14 23:57 ` Rob Herring (Arm)
2025-01-14 22:01 ` [PATCH v5 03/10] dt-bindings: gpio: ast2400-gpio: Add hogs parsing Ninad Palsule
2025-01-14 23:57 ` Rob Herring (Arm)
2025-01-16 15:04 ` Ninad Palsule
2025-01-16 19:57 ` Rob Herring
2025-01-16 20:37 ` Ninad Palsule [this message]
2025-01-15 8:45 ` Krzysztof Kozlowski
2025-01-15 14:24 ` Rob Herring
2025-01-15 20:30 ` Krzysztof Kozlowski
[not found] ` <a164ab0e-1cdf-427e-bfb7-f5614be5b0fa@linux.ibm.com>
2025-01-16 10:38 ` Krzysztof Kozlowski
[not found] ` <10c06fec-b721-4a7f-b105-c3c4c8358a47@linux.ibm.com>
2025-01-16 14:48 ` Rob Herring
2025-01-16 15:10 ` Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 04/10] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 05/10] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 06/10] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 07/10] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 08/10] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 09/10] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-01-14 22:01 ` [PATCH v5 10/10] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-01-15 1:40 ` [PATCH v5 00/10] DTS updates for system1 BMC Rob Herring (Arm)
2025-01-16 15:15 ` Ninad Palsule
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=c61740c8-8dd3-4d59-8553-1dea4cbd5c93@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--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®