From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Hanjun Guo <guohanjun@huawei.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pankaj Bansal <pankaj.bansal@nxp.com>,
linux-acpi@vger.kernel.org, John Garry <john.garry@huawei.com>,
linuxarm@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] ACPI/IORT: Workaround for IORT ID count "minus one" issue
Date: Fri, 10 Jan 2020 10:39:24 +0000 [thread overview]
Message-ID: <20200110103924.GA15314@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <4cee4a91-6459-819b-d4d4-f5e8899103b9@huawei.com>
On Fri, Jan 10, 2020 at 02:22:22PM +0800, Hanjun Guo wrote:
[...]
> > I am fine either way. We need test coverage since I feel this may
> > break a number of systems (ie I don't think it should be merged as
> > a fix).
>
> Will you resend this patch with commit log and the updated code? or
> let me do that? Both are ok to me, let's get it tested for longer time
> if we merge it ASAP.
I will write the commit log in reply to the original patch, please
update the code and repost the whole thing (it is better you
repost it to avoid confusing Catalin and Will).
This technically is not a fix; we can try to get it into v5.6 but
I am a bit nervous since it can break other platforms, we have to
fix it though so better sooner than later.
Thanks,
Lorenzo
next prev parent reply other threads:[~2020-01-10 10:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 12:27 [PATCH v1] ACPI/IORT: Workaround for IORT ID count "minus one" issue Hanjun Guo
2020-01-02 11:18 ` John Garry
2020-01-03 10:20 ` Hanjun Guo
2020-01-06 17:19 ` Robin Murphy
2020-01-07 12:03 ` Hanjun Guo
2020-01-09 16:02 ` Lorenzo Pieralisi
2020-01-10 6:22 ` Hanjun Guo
2020-01-10 10:39 ` Lorenzo Pieralisi [this message]
2020-01-10 10:51 ` Robin Murphy
2020-01-10 12:11 ` Lorenzo Pieralisi
2020-01-13 7:04 ` Hanjun Guo
2020-01-13 9:34 ` John Garry
2020-01-14 7:19 ` Hanjun Guo
2020-01-14 9:47 ` John Garry
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=20200110103924.GA15314@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=guohanjun@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=pankaj.bansal@nxp.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@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).