linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-acpi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Hanjun Guo <hanjun.guo@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
Subject: Re: [PATCH 1/3] ACPI/IORT: Remove leftover ACPI_IORT_SMMU_V3_PXM_VALID guard
Date: Tue, 10 Oct 2017 15:59:32 +0800	[thread overview]
Message-ID: <59DC7DE4.90409@huawei.com> (raw)
In-Reply-To: <1507038811-23382-2-git-send-email-lorenzo.pieralisi@arm.com>

On 2017/10/3 21:53, Lorenzo Pieralisi wrote:
> The conditional ACPI_IORT_SMMU_V3_PXM_VALID guard around
> arm_smmu_v3_set_proximity() was added to manage a cross tree
> ACPICA merge dependency; with ACPICA changes merged in:
>
> commit c944230064eb ("ACPICA: iasl: Update to IORT SMMUv3
> disassembling")
>
> the guard has become useless. Remove it.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Hanjun Guo <hanjun.guo@linaro.org>
> Cc: Sudeep Holla <sudeep.holla@arm.com>
> Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
>

Acked-by: Hanjun Guo <hanjun.guo@linaro.org>


  reply	other threads:[~2017-10-10  8:01 UTC|newest]

Thread overview: 10+ 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 ` [PATCH 1/3] ACPI/IORT: Remove leftover ACPI_IORT_SMMU_V3_PXM_VALID guard Lorenzo Pieralisi
2017-10-10  7:59   ` Hanjun Guo [this message]
2017-10-03 13:53 ` [PATCH 2/3] ACPI/IORT: Improve functions return type/storage class specifier indentation Lorenzo Pieralisi
2017-10-10  8:03   ` Hanjun Guo
2017-10-10  9:03     ` Hanjun Guo
2017-10-10 11:17       ` 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-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=59DC7DE4.90409@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=ganapatrao.kulkarni@cavium.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 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).