From: Hanjun Guo <guohanjun@huawei.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-acpi@vger.kernel.org
Cc: Hanjun Guo <hanjun.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 3/3] ACPI/IORT: Make platform devices initialization code SMMU agnostic
Date: Tue, 10 Oct 2017 17:27:01 +0800 [thread overview]
Message-ID: <59DC9265.3070709@huawei.com> (raw)
In-Reply-To: <1507038811-23382-4-git-send-email-lorenzo.pieralisi@arm.com>
On 2017/10/3 21:53, Lorenzo Pieralisi wrote:
> The way current IORT code initializes platform devices for SMMU nodes
> is somewhat tied (mostly for naming convention) to the SMMU nodes
> themselves but it need not be in that it is completely generic and
> can easily be made so by structures renaming and code reshuffling.
>
> Rework IORT platform devices initialization code to make the functions
> and data structures SMMU agnostic.
>
> No functional changes intended.
This will be good preparation for PMCG driver support, with my comments
in patch 2/3 fixed,
Acked-by: Hanjun Guo <hanjun.guo@linaro.org>
Thanks
Hanjun
WARNING: multiple messages have this Message-ID (diff)
From: guohanjun@huawei.com (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ACPI/IORT: Make platform devices initialization code SMMU agnostic
Date: Tue, 10 Oct 2017 17:27:01 +0800 [thread overview]
Message-ID: <59DC9265.3070709@huawei.com> (raw)
In-Reply-To: <1507038811-23382-4-git-send-email-lorenzo.pieralisi@arm.com>
On 2017/10/3 21:53, Lorenzo Pieralisi wrote:
> The way current IORT code initializes platform devices for SMMU nodes
> is somewhat tied (mostly for naming convention) to the SMMU nodes
> themselves but it need not be in that it is completely generic and
> can easily be made so by structures renaming and code reshuffling.
>
> Rework IORT platform devices initialization code to make the functions
> and data structures SMMU agnostic.
>
> No functional changes intended.
This will be good preparation for PMCG driver support, with my comments
in patch 2/3 fixed,
Acked-by: Hanjun Guo <hanjun.guo@linaro.org>
Thanks
Hanjun
next prev parent reply other threads:[~2017-10-10 9:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:53 [PATCH 0/3] ACPI/IORT: Clean-up/rework for v4.15 Lorenzo Pieralisi
2017-10-03 13:53 ` Lorenzo Pieralisi
2017-10-03 13:53 ` [PATCH 1/3] ACPI/IORT: Remove leftover ACPI_IORT_SMMU_V3_PXM_VALID guard Lorenzo Pieralisi
2017-10-03 13:53 ` Lorenzo Pieralisi
2017-10-10 7:59 ` Hanjun Guo
2017-10-10 7:59 ` Hanjun Guo
2017-10-03 13:53 ` [PATCH 2/3] ACPI/IORT: Improve functions return type/storage class specifier indentation Lorenzo Pieralisi
2017-10-03 13:53 ` Lorenzo Pieralisi
2017-10-10 8:03 ` Hanjun Guo
2017-10-10 8:03 ` Hanjun Guo
2017-10-10 9:03 ` Hanjun Guo
2017-10-10 9:03 ` Hanjun Guo
2017-10-10 11:17 ` Lorenzo Pieralisi
2017-10-10 11:17 ` Lorenzo Pieralisi
2017-10-10 11:16 ` Lorenzo Pieralisi
2017-10-10 11:16 ` Lorenzo Pieralisi
2017-10-03 13:53 ` [PATCH 3/3] ACPI/IORT: Make platform devices initialization code SMMU agnostic Lorenzo Pieralisi
2017-10-03 13:53 ` Lorenzo Pieralisi
2017-10-10 9:27 ` Hanjun Guo [this message]
2017-10-10 9:27 ` Hanjun Guo
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=59DC9265.3070709@huawei.com \
--to=guohanjun@huawei.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.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 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.