From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v6] dt-bindings: gpio: aspeed,ast2400-gpio: Convert to DT schema
Date: Mon, 04 Mar 2024 14:06:55 +1030 [thread overview]
Message-ID: <33f423783b71a4e4dd6e8c37a8909a69c25fb24c.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAMRc=Mfa1uUhkPNpLdcMsGC4=G+_MGzaxXRL7UVdfKJD_zF0+w@mail.gmail.com>
On Fri, 2024-03-01 at 09:18 +0100, Bartosz Golaszewski wrote:
> On Fri, Mar 1, 2024 at 12:23?AM Andrew Jeffery
> <andrew@codeconstruct.com.au> wrote:
> >
> > On Thu, 2024-02-29 at 09:52 +0100, Bartosz Golaszewski wrote:
> > > On Thu, Feb 29, 2024 at 4:21?AM Andrew Jeffery
> > > <andrew@codeconstruct.com.au> wrote:
> > > >
> > > > On Wed, 2024-02-28 at 08:47 +0100, Krzysztof Kozlowski wrote:
> > > > >
> > > > > You still have way too many examples. One is enough, two is still okay.
> > > > > We really do not want more of examples with minor differences.
> > > >
> > > > Noted, I'll keep them to a minimum in the future.
> > > >
> > >
> > > As in: I'll still send a v7? I can trim the examples when applying,
> > > just tell me which ones to drop.
> >
> > Ah, thanks. I wasn't planning to send a v7 given the R-b tag from
> > Krzysztof for v6. I intended for "in the future" to mean for patches
> > converting other bindings to DT schema. But if you're keen to trim some
> > examples out I'd drop the aspeed,ast2400-gpio and aspeed,ast2500-gpio
> > nodes, keeping just the aspeed,ast2600-gpio example.
> >
> > Andrew
>
> It's ok, I applied it as is.
Thanks!
Andrew
prev parent reply other threads:[~2024-03-04 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 0:30 [PATCH v6] dt-bindings: gpio: aspeed,ast2400-gpio: Convert to DT schema Andrew Jeffery
2024-02-28 7:47 ` Krzysztof Kozlowski
2024-02-29 3:21 ` Andrew Jeffery
2024-02-29 8:52 ` Bartosz Golaszewski
2024-02-29 23:23 ` Andrew Jeffery
2024-03-01 8:18 ` Bartosz Golaszewski
2024-03-04 3:36 ` 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=33f423783b71a4e4dd6e8c37a8909a69c25fb24c.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=linux-aspeed@lists.ozlabs.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).