From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: guohanjun@huawei.com, sudeep.holla@arm.com, rafael@kernel.org,
linux@armlinux.org.uk, lenb@kernel.org, robert.moore@intel.com,
james.morse@arm.com, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, patches@amperecomputing.com,
scott@os.amperecomputing.com, darren@os.amperecomputing.com
Subject: Re: [PATCH v5 RESEND 0/2] ACPI: Arm Generic Diagnostic Dump and Reset device
Date: Tue, 8 Mar 2022 19:18:39 +0000 [thread overview]
Message-ID: <YiesD0vwbAOQGaGK@lpieralisi> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2203071424290.3354@ubuntu200401>
On Mon, Mar 07, 2022 at 02:29:10PM -0800, Ilkka Koskinen wrote:
[...]
> > > Would you prefer this version, which doesn't have platform
> > > device/driver any more?
> >
> > I thought about that and in order to keep consistency it is better to
> > keep the platform device model, so please resend the latest version
> > platform device based and I will ACK it (hopefully it is not too late
> > for v5.18).
>
> Sure, I can do that. Just one question, do you still prefer agdi_init()
> getting called from acpi_init() or via device_initcall()?
In acpi_init(), thanks.
Lorenzo
prev parent reply other threads:[~2022-03-08 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 5:40 [PATCH v5 RESEND 0/2] ACPI: Arm Generic Diagnostic Dump and Reset device Ilkka Koskinen
2022-03-04 5:40 ` [PATCH v5 RESEND 1/2] ACPI: tables: Add AGDI to the list of known table signatures Ilkka Koskinen
2022-03-04 5:40 ` [PATCH v5 RESEND 2/2] ACPI: AGDI: Add support for Arm Generic Diagnostic Dump and Reset device Ilkka Koskinen
2022-03-04 15:13 ` [PATCH v5 RESEND 0/2] ACPI: " Lorenzo Pieralisi
2022-03-07 22:29 ` Ilkka Koskinen
2022-03-08 19:18 ` Lorenzo Pieralisi [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=YiesD0vwbAOQGaGK@lpieralisi \
--to=lorenzo.pieralisi@arm.com \
--cc=darren@os.amperecomputing.com \
--cc=guohanjun@huawei.com \
--cc=ilkka@os.amperecomputing.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=patches@amperecomputing.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=scott@os.amperecomputing.com \
--cc=sudeep.holla@arm.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