From: Hanjun Guo <guohanjun@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: Zenghui Yu <yuzenghui@huawei.com>, <lorenzo.pieralisi@arm.com>,
<sudeep.holla@arm.com>, <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wanghaibin.wang@huawei.com>
Subject: Re: [PATCH v2 0/2] ACPI/IORT: Code cleanups
Date: Wed, 2 Sep 2020 19:55:48 +0800 [thread overview]
Message-ID: <bcbc099d-8a50-95c1-ad72-709368e326b2@huawei.com> (raw)
In-Reply-To: <20200902094806.GA5567@willie-the-truck>
On 2020/9/2 17:48, Will Deacon wrote:
> On Wed, Sep 02, 2020 at 05:17:43PM +0800, Hanjun Guo wrote:
>> +Cc Will
>>
>> On 2020/8/18 17:16, Hanjun Guo wrote:
>>> On 2020/8/18 14:36, Zenghui Yu wrote:
>>>> * From v1 [1]:
>>>> - As pointed out by Hanjun, remove two now unused inline functions.
>>>> Compile tested with CONFIG_IOMMU_API is not selected.
>>>>
>>>> [1] https://lore.kernel.org/r/20200817105946.1511-1-yuzenghui@huawei.com
>>>>
>>>> Zenghui Yu (2):
>>>> ACPI/IORT: Drop the unused @ops of iort_add_device_replay()
>>>> ACPI/IORT: Remove the unused inline functions
>>>>
>>>> drivers/acpi/arm64/iort.c | 10 ++--------
>>>> 1 file changed, 2 insertions(+), 8 deletions(-)
>>>
>>> Nice cleanup.
>>>
>>> Acked-by: Hanjun Guo <guohanjun@huawei.com>
>>
>> Will, would you mind taking this patch set via ARM64 tree?
>
> Sure, no problem. I'll queue this for 5.10 later this week.
Thanks!
Hanjun
next prev parent reply other threads:[~2020-09-02 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 6:36 Zenghui Yu
2020-08-18 6:36 ` [PATCH v2 1/2] ACPI/IORT: Drop the unused @ops of iort_add_device_replay() Zenghui Yu
2020-08-18 6:36 ` [PATCH v2 2/2] ACPI/IORT: Remove the unused inline functions Zenghui Yu
2020-08-18 9:16 ` [PATCH v2 0/2] ACPI/IORT: Code cleanups Hanjun Guo
2020-09-02 9:17 ` Hanjun Guo
2020-09-02 9:48 ` Will Deacon
2020-09-02 11:55 ` Hanjun Guo [this message]
2020-09-02 9:29 ` Lorenzo Pieralisi
2020-09-07 16:05 ` Will Deacon
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=bcbc099d-8a50-95c1-ad72-709368e326b2@huawei.com \
--to=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sudeep.holla@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®