From: Rob Herring <robh@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: gpio: st,nomadik-gpio: Add missing "#interrupt-cells" to example
Date: Wed, 2 Oct 2024 09:22:03 -0500 [thread overview]
Message-ID: <CAL_JsqK8HxEYicNKu0zhfWKY8Ui9657PWEDFr8maSWKaeJijXg@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=McdAwEUCDouUeOENt36LZ+d4Fd=yeqzm9dn83XSqZpQFA@mail.gmail.com>
On Wed, Oct 2, 2024 at 8:32 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>
> On Wed, Oct 2, 2024 at 3:04 PM Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > On Wed, Sep 25, 2024 at 7:35 PM Rob Herring (Arm) <robh@kernel.org> wrote:
> >
> > > Enabling dtc interrupt_provider check reveals the example is missing the
> > > "#interrupt-cells" property as it is a dependency of
> > > "interrupt-controller".
> > >
> > > Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> >
> > Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > Can you please merge this into the DT git tree?
> >
> > Yours,
> > Linus Walleij
>
> It's already upstream. I learned it when I tried picking it up. Rob:
> any chance you could send b4 notifications when applying patches to
> your tree?
It's not upstream. The ep9301 one is because Arnd applied it.
I do send notifications when applying things. Not using b4 though
because I haven't converted my scripts to it for that yet.
Rob
next prev parent reply other threads:[~2024-10-02 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 17:35 [PATCH] dt-bindings: gpio: st,nomadik-gpio: Add missing "#interrupt-cells" to example Rob Herring (Arm)
2024-09-26 16:55 ` Conor Dooley
2024-10-02 13:04 ` Linus Walleij
2024-10-02 13:32 ` Bartosz Golaszewski
2024-10-02 14:22 ` Rob Herring [this message]
2024-10-02 14:29 ` Bartosz Golaszewski
2024-10-02 14:28 ` Bartosz Golaszewski
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=CAL_JsqK8HxEYicNKu0zhfWKY8Ui9657PWEDFr8maSWKaeJijXg@mail.gmail.com \
--to=robh@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).