openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: DTML <devicetree@vger.kernel.org>,
	Tomer Maimon <tmaimon77@gmail.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 00/10] Initial support for Nuvoton WPCM450 BMC SoC
Date: Tue, 6 Apr 2021 17:15:01 +0200	[thread overview]
Message-ID: <CAK8P3a0VfnUucvZNkA9PdxrWiYUOkisV00v-375PmgQYp4aXoQ@mail.gmail.com> (raw)
In-Reply-To: <20210406120921.2484986-1-j.neuschaefer@gmx.net>

On Tue, Apr 6, 2021 at 2:09 PM Jonathan Neuschäfer
<j.neuschaefer@gmx.net> wrote:
>
> This series adds basic support for the Nuvoton WPCM450 BMC SoC. It's an older
> SoC but still commonly found on eBay, mostly in Supermicro X9 server boards.
>
> Third-party documentation is available at: https://github.com/neuschaefer/wpcm450/wiki
>
> Patches 1-4 add devicetree bindings for the WPCM450 SoC and its various parts.
> Patches 5-7 add arch and driver support. Patches 8 and 9 add a devicetree for
> the SoC and a board based on it. Patch 10 finally updates the MAINTAINERS file.
>
> Patch 2 requires "dt-bindings: arm: Convert nuvoton,npcm750 binding to YAML"
> (https://lore.kernel.org/lkml/20210320164023.614059-1-j.neuschaefer@gmx.net/)

Hi Jonathan,

It appears these patches are doing roughly the right thing, and we may still
be able to get them into v5.13, but I'm not sure what your plan for maintaining
them is. The two options are that you either send your patches to be picked up
by Joel, or you send everything directly to soc@kernel.org once it's fully
reviewed.

I only noticed your series when patch 9/10 made it into the soc@kernel.org
patchwork because of the Cc, but none of the other ones did.

If you end up with the second option, we can go through what this involves
off-list.

Regarding the Cc:soc@kernel.org, please add that only for patches that
are already reviewed and ready to be picked up, ideally with a cover letter
that describes what the plan is for merging. If you need me to review the
platform code, use my arnd@arndb.de or arnd@kernel.org addresses.

          Arnd

  parent reply	other threads:[~2021-04-06 15:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 12:09 [PATCH v2 00/10] Initial support for Nuvoton WPCM450 BMC SoC Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 01/10] dt-bindings: vendor-prefixes: Add Supermicro Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 02/10] dt-bindings: arm: npcm: Add nuvoton, wpcm450 compatible string Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 03/10] dt-bindings: interrupt-controller: Add nuvoton, wpcm450-aic Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 04/10] dt-bindings: watchdog: npcm: Add nuvoton, wpcm450-wdt Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 05/10] ARM: npcm: Introduce Nuvoton WPCM450 SoC Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 06/10] irqchip: Add driver for WPCM450 interrupt controller Jonathan Neuschäfer
2021-04-07 11:11   ` Marc Zyngier
2021-04-07 12:06     ` Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 07/10] watchdog: npcm: Add support for WPCM450 Jonathan Neuschäfer
2021-04-06 13:42   ` Guenter Roeck
2021-04-06 12:09 ` [PATCH v2 08/10] ARM: dts: Add devicetree for Nuvoton WPCM450 BMC chip Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 09/10] ARM: dts: Add devicetree for Supermicro X9SCi-LN4F based on WPCM450 Jonathan Neuschäfer
2021-04-06 12:09 ` [PATCH v2 10/10] MAINTAINERS: Add entry for Nuvoton WPCM450 Jonathan Neuschäfer
2021-04-06 15:15 ` Arnd Bergmann [this message]
2021-04-06 21:58   ` [PATCH v2 00/10] Initial support for Nuvoton WPCM450 BMC SoC Jonathan Neuschäfer
2021-04-09  4:37     ` Joel Stanley
2021-04-09  7:57       ` Jonathan Neuschäfer
2021-04-09  8:04         ` Arnd Bergmann
2021-04-07 12:31 ` Marc Zyngier

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=CAK8P3a0VfnUucvZNkA9PdxrWiYUOkisV00v-375PmgQYp4aXoQ@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tmaimon77@gmail.com \
    /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).