All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Davis" <afd@ti.com>, "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 v4 0/9] TI-Nspire cleanups
Date: Wed, 02 Nov 2022 13:42:54 +0100	[thread overview]
Message-ID: <1756ff9a-babc-40c6-8002-9f464e023c52@app.fastmail.com> (raw)
In-Reply-To: <20221101215804.16262-1-afd@ti.com>

On Tue, Nov 1, 2022, at 22:57, 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).

Hi Andrew,

Thanks for the cleanup series. All of this looks reasonable to
me, but we need to decide how to merge it upstream. I can
pick up the patches directly into the soc tree once everybody
is happy with the latest version, though usually I prefer
to take the patches or pull requests from the person listed
in the MAINTAINERS file.I'm happy to

It looks like there has never been a maintainer listed for
nspire, so it would be good to fix that. Between yourself,
Daniel and Fabian, can you find one or more people that
are willing to be listed as either reviewer or maintainer
for future patches, and decide what status you want the
platform to be listed at ("Maintained" or "Odd Fixes" I
assume)?

       Arnd

WARNING: multiple messages have this Message-ID (diff)
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Davis" <afd@ti.com>, "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 v4 0/9] TI-Nspire cleanups
Date: Wed, 02 Nov 2022 13:42:54 +0100	[thread overview]
Message-ID: <1756ff9a-babc-40c6-8002-9f464e023c52@app.fastmail.com> (raw)
In-Reply-To: <20221101215804.16262-1-afd@ti.com>

On Tue, Nov 1, 2022, at 22:57, 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).

Hi Andrew,

Thanks for the cleanup series. All of this looks reasonable to
me, but we need to decide how to merge it upstream. I can
pick up the patches directly into the soc tree once everybody
is happy with the latest version, though usually I prefer
to take the patches or pull requests from the person listed
in the MAINTAINERS file.I'm happy to

It looks like there has never been a maintainer listed for
nspire, so it would be good to fix that. Between yourself,
Daniel and Fabian, can you find one or more people that
are willing to be listed as either reviewer or maintainer
for future patches, and decide what status you want the
platform to be listed at ("Maintained" or "Odd Fixes" I
assume)?

       Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-11-02 12:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 21:57 [PATCH v4 0/9] TI-Nspire cleanups Andrew Davis
2022-11-01 21:57 ` Andrew Davis
2022-11-01 21:57 ` [PATCH v4 1/9] dt-bindings: mfd: Add TI-Nspire misc registers Andrew Davis
2022-11-01 21:57   ` Andrew Davis
2022-11-02 17:35   ` Rob Herring
2022-11-02 17:35     ` Rob Herring
2022-11-02 19:05     ` Andrew Davis
2022-11-02 19:05       ` Andrew Davis
2022-11-02 21:26       ` Rob Herring
2022-11-02 21:26         ` Rob Herring
2022-11-03  1:13         ` Andrew Davis
2022-11-03  1:13           ` Andrew Davis
2022-11-01 21:57 ` [PATCH v4 2/9] ARM: dts: nspire: Use syscon-reboot to handle restart Andrew Davis
2022-11-01 21:57   ` Andrew Davis
2022-11-01 21:57 ` [PATCH v4 3/9] ARM: dts: nspire: Fix cpu node to conform with DT binding Andrew Davis
2022-11-01 21:57   ` Andrew Davis
2022-11-01 21:57 ` [PATCH v4 4/9] ARM: dts: nspire: Fix sram " Andrew Davis
2022-11-01 21:57   ` Andrew Davis
2022-11-01 21:58 ` [PATCH v4 5/9] ARM: dts: nspire: Fix vbus_reg " Andrew Davis
2022-11-01 21:58   ` Andrew Davis
2022-11-01 21:58 ` [PATCH v4 6/9] ARM: dts: nspire: Fix uart " Andrew Davis
2022-11-01 21:58   ` Andrew Davis
2022-11-01 21:58 ` [PATCH v4 7/9] ARM: dts: nspire: Use MATRIX_KEY macro for linux,keymap Andrew Davis
2022-11-01 21:58   ` Andrew Davis
2022-11-03  4:07   ` Dmitry Torokhov
2022-11-03  4:07     ` Dmitry Torokhov
2022-11-03 16:29     ` Andrew Davis
2022-11-03 16:29       ` Andrew Davis
2022-11-01 21:58 ` [PATCH v4 8/9] ARM: nspire: Use syscon-reboot to handle restart Andrew Davis
2022-11-01 21:58   ` Andrew Davis
2022-11-01 21:58 ` [PATCH v4 9/9] ARM: nspire: Remove unused header file mmio.h Andrew Davis
2022-11-01 21:58   ` Andrew Davis
2022-11-02 12:42 ` Arnd Bergmann [this message]
2022-11-02 12:42   ` [PATCH v4 0/9] TI-Nspire cleanups Arnd Bergmann

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=1756ff9a-babc-40c6-8002-9f464e023c52@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=afd@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.