From: Hanjun Guo <guohanjun@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Sudeep Holla" <sudeep.holla@arm.com>,
Will Deacon <will@kernel.org>
Cc: <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Hanjun Guo <guohanjun@huawei.com>
Subject: [PATCH] ACPI: IORT: Add extra message "applying workaround" for off-by-1 issue
Date: Thu, 7 May 2020 21:41:08 +0800 [thread overview]
Message-ID: <1588858868-18039-1-git-send-email-guohanjun@huawei.com> (raw)
As we already applied a workaround for the off-by-1 issue,
it's good to add extra message "applying workaround" to
make people less uneasy to see such message in the boot log.
Signed-off-by: Hanjun Guo <guohanjun@huawei.com>
---
Based on top of for-next/acpi branch of ARM64 repo
drivers/acpi/arm64/iort.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
index b011d25..f3d492a 100644
--- a/drivers/acpi/arm64/iort.c
+++ b/drivers/acpi/arm64/iort.c
@@ -328,7 +328,7 @@ static int iort_id_map(struct acpi_iort_id_mapping *map, u8 type, u32 rid_in,
* Otherwise, things are *really* broken, and we just disregard
* duplicate matches entirely to retain compatibility.
*/
- pr_err(FW_BUG "[map %p] conflicting mapping for input ID 0x%x\n",
+ pr_err(FW_BUG "[map %p] conflicting mapping for input ID 0x%x, applying workaround\n",
map, rid_in);
if (rid_in != map->input_base)
return -ENXIO;
--
1.7.12.4
next reply other threads:[~2020-05-07 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 13:41 Hanjun Guo [this message]
2020-05-07 13:49 ` [PATCH] ACPI: IORT: Add extra message "applying workaround" for off-by-1 issue Ard Biesheuvel
2020-05-07 13:53 ` Hanjun Guo
2020-05-07 14:02 ` Hanjun Guo
2020-05-07 16:39 ` Ard Biesheuvel
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=1588858868-18039-1-git-send-email-guohanjun@huawei.com \
--to=guohanjun@huawei.com \
--cc=ardb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
/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).