From: Andrew Davis <afd@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Daniel Tang <dt.tangr@gmail.com>,
Fabian Vogt <fabian@ritter-vogt.de>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/9] TI-Nspire cleanups
Date: Mon, 23 Jan 2023 17:56:49 -0600 [thread overview]
Message-ID: <3ab320ef-dfbb-eee4-f895-6f1caa6cc66f@ti.com> (raw)
In-Reply-To: <f8922fbc-13cc-4f08-a8e8-08d39ab7d63c@app.fastmail.com>
On 1/23/23 3:57 PM, Arnd Bergmann wrote:
> On Mon, Jan 23, 2023, at 22:49, Andrew Davis wrote:
>> Hello all,
>>
>> This series is an extended version of the series started here[0]
>> and here[1].
>>
>> We break out what was the first patch into one for DTS change and
>> one for code changes as suggested by Krzysztof. Those are now patches
>> 2 and 8 of this series (I kept the ACKs, hope that is okay).
>>
>> As also pointed out by Krzysztof syscon nodes need a specific
>> compatible, add that as patch 1.
>>
>> While I was adding that, I noticed some other dtbs_check issues,
>> so while here fixed some of those up too (patches 3-6).
>
> Looks all good to me, if there are no final comments within the
> next few days, can you send this all to:soc@kernel.org, either as
> separate patches or as two pull requests (dts and code) based
> on 6.2-rc-1?
>
Sure thing.
> I think I previously commented on the lack of an entry in
> the MAINTAINERS. It would be nice to have one more patch to
> add this, whichever way you want to split this with Daniel,
> adding one or both of you as maintainer and/or reviewer.
> I'd keep that separate from this series though, to not hold
> it up any longer.
>
Daniel,
Do you want to do this? If not I can add myself as a reviewer, the
point of this series is to boil down the support to just the DTS file,
at which point hopefully we won't need too much maintenance.
Andrew
> Arnd
next prev parent reply other threads:[~2023-01-23 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 21:49 Andrew Davis
2023-01-23 21:49 ` [PATCH v5 1/9] dt-bindings: mfd: Add TI-Nspire misc registers Andrew Davis
2023-01-25 19:56 ` Rob Herring
2023-01-23 21:49 ` [PATCH v5 2/9] ARM: dts: nspire: Use syscon-reboot to handle restart Andrew Davis
2023-01-23 21:49 ` [PATCH v5 3/9] ARM: dts: nspire: Fix cpu node to conform with DT binding Andrew Davis
2023-01-23 21:49 ` [PATCH v5 4/9] ARM: dts: nspire: Fix sram " Andrew Davis
2023-01-23 21:49 ` [PATCH v5 5/9] ARM: dts: nspire: Fix vbus_reg " Andrew Davis
2023-01-23 21:49 ` [PATCH v5 6/9] ARM: dts: nspire: Fix uart " Andrew Davis
2023-01-23 21:49 ` [PATCH v5 7/9] ARM: dts: nspire: Use MATRIX_KEY macro for linux,keymap Andrew Davis
2023-01-23 21:49 ` [PATCH v5 8/9] ARM: nspire: Use syscon-reboot to handle restart Andrew Davis
2023-01-23 21:49 ` [PATCH v5 9/9] ARM: nspire: Remove unused header file mmio.h Andrew Davis
2023-01-23 21:57 ` [PATCH v5 0/9] TI-Nspire cleanups Arnd Bergmann
2023-01-23 23:56 ` Andrew Davis [this message]
2023-01-28 2:00 ` Daniel Tang
2023-01-28 11:24 ` Fabian Vogt
2023-01-24 10:33 ` Lee Jones
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=3ab320ef-dfbb-eee4-f895-6f1caa6cc66f@ti.com \
--to=afd@ti.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dt.tangr@gmail.com \
--cc=fabian@ritter-vogt.de \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®