devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Brad Larson" <blarson@amd.com>
Cc: "Adrian Hunter" <adrian.hunter@intel.com>,
	alcooperx@gmail.com,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	brendan.higgins@linux.dev,
	"Brian Norris" <briannorris@chromium.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"David Gow" <davidgow@google.com>,
	devicetree@vger.kernel.org,
	"Serge Semin" <fancer.lancer@gmail.com>,
	"Greg Ungerer" <gerg@linux-m68k.org>,
	gsomlo@gmail.com, "Hal Feng" <hal.feng@starfivetech.com>,
	"Hitomi Hasegawa" <hasegawa-hitomi@fujitsu.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Joel Stanley" <joel@jms.id.au>,
	"Emil Renner Berthing" <kernel@esmil.dk>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	krzysztof.kozlowski+dt@linaro.org,
	"Lee Jones" <lee.jones@linaro.org>, "Lee Jones" <lee@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"linux-mmc @ vger . kernel . org" <linux-mmc@vger.kernel.org>,
	linux-spi@vger.kernel.org,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Samuel Holland" <samuel@sholland.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	suravee.suthikulpanit@amd.com,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Tony Huang" <tonyhuang.sunplus@gmail.com>,
	"Ulf Hansson" <ulf.hansson@linaro.org>,
	vaishnav.a@ti.com, "Walker Chen" <walker.chen@starfivetech.com>,
	"Will Deacon" <will@kernel.org>,
	"Yinbo Zhu" <zhuyinbo@loongson.cn>
Subject: Re: [PATCH v16 6/6] soc: amd: Add support for AMD Pensando SoC Controller
Date: Tue, 26 Sep 2023 19:51:22 +0200	[thread overview]
Message-ID: <aa1bb018-cfdf-43de-a1d0-47b11dd626fa@app.fastmail.com> (raw)
In-Reply-To: <20230926174716.41705-1-blarson@amd.com>

On Tue, Sep 26, 2023, at 19:47, Brad Larson wrote:
> On Fri, Sep 22, 2023, at 06:24:00 -0400, Arnd Bergmann wrote:
>> On Wed, Sep 13, 2023, at 17:49, Brad Larson wrote:
>> I'm sorry I've been out of the loop for so long, and I hope
>> we can find a way to manage your SoC support soon. My impression
>> is that the normal support patches (1, 3, 4, and 5) are largely
>> uncontroversial, while the SoC controller support seems like
>> we are still not converging onto something that is ready to
>> merge, so I would suggest you split the two parts and send
>> the basic support for inclusion in linux-6.7 while we continue
>> to discuss the soc controller driver.
>
> I've sent a patchset with only patches 1, 3, 4, and 5.  Correctness
> is the priority for upstream inclusion.

Ok, I took a look already and it all looks good. I should
be able to pick it up into linux-next in the next few days
when I open my branches for 6.7.

> I'll redirect and reframe what the SoC driver is doing to
> #armlinux IRC to find an appropriate solution.

Ok.

    Arnd

      reply	other threads:[~2023-09-26 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 21:49 [PATCH v16 0/6] Support AMD Pensando Elba SoC Brad Larson
2023-09-13 21:49 ` [PATCH v16 1/6] dt-bindings: arm: add AMD Pensando boards Brad Larson
2023-09-13 21:49 ` [PATCH v16 2/6] dt-bindings: soc: amd: amd,pensando-elba-ctrl: Add Pensando SoC Controller Brad Larson
2023-09-13 21:49 ` [PATCH v16 3/6] MAINTAINERS: Add entry for AMD PENSANDO Brad Larson
2023-09-13 21:49 ` [PATCH v16 4/6] arm64: Add config for AMD Pensando SoC platforms Brad Larson
2023-09-13 21:49 ` [PATCH v16 5/6] arm64: dts: Add AMD Pensando Elba SoC support Brad Larson
2023-09-14 18:52   ` Rob Gardner
2023-09-13 21:49 ` [PATCH v16 6/6] soc: amd: Add support for AMD Pensando SoC Controller Brad Larson
2023-09-21 15:19   ` Andy Shevchenko
2023-09-26 20:05     ` Brad Larson
2023-09-27 12:59       ` Andy Shevchenko
2023-09-22 10:24   ` Arnd Bergmann
2023-09-25  8:51     ` Andy Shevchenko
2023-09-26 17:47     ` Brad Larson
2023-09-26 17:51       ` Arnd Bergmann [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=aa1bb018-cfdf-43de-a1d0-47b11dd626fa@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=adrian.hunter@intel.com \
    --cc=alcooperx@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=blarson@amd.com \
    --cc=brendan.higgins@linux.dev \
    --cc=briannorris@chromium.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=davidgow@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=gerg@linux-m68k.org \
    --cc=gsomlo@gmail.com \
    --cc=hal.feng@starfivetech.com \
    --cc=hasegawa-hitomi@fujitsu.com \
    --cc=j.neuschaefer@gmx.net \
    --cc=joel@jms.id.au \
    --cc=kernel@esmil.dk \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=skhan@linuxfoundation.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=tonyhuang.sunplus@gmail.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vaishnav.a@ti.com \
    --cc=walker.chen@starfivetech.com \
    --cc=will@kernel.org \
    --cc=zhuyinbo@loongson.cn \
    /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).