From: Dave Jiang <dave.jiang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, linux-cxl@vger.kernel.org
Cc: Robert Richter <rrichter@amd.com>
Subject: Re: [PATCH] cxl/acpi: Warn about an invalid CHBCR in an existing CHBS entry
Date: Mon, 5 Dec 2022 14:01:04 -0700 [thread overview]
Message-ID: <08d4f315-4c91-225b-d2dd-98ed111ce950@intel.com> (raw)
In-Reply-To: <167027170051.3542509.10494781536638424397.stgit@dwillia2-xfh.jf.intel.com>
On 12/5/2022 1:21 PM, Dan Williams wrote:
> From: Robert Richter <rrichter@amd.com>
>
> After parsing for a CHBCR in cxl_get_chbcr() the case of (ctx.chbcr ==
> CXL_RESOURCE_NONE) is a slighly different error reason than the
> !ctx.chbcr case. In the first case the CHBS was found but the CHBCR
> was invalid or something else failed to determine it, while in the
> latter case no CHBS entry exists at all.
>
> Update the warning message to reflect this. The log messages for both
> cases can be differentiated now and the reason for a failure can be
> determined better.
>
> Signed-off-by: Robert Richter <rrichter@amd.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/acpi.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> index 420e322c85a1..f495f3ce45d1 100644
> --- a/drivers/cxl/acpi.c
> +++ b/drivers/cxl/acpi.c
> @@ -455,7 +455,8 @@ static int add_host_bridge_dport(struct device *match, void *arg)
> dev_dbg(match, "RCRB found for UID %lld: %pa\n", uid, &ctx.rcrb);
>
> if (ctx.chbcr == CXL_RESOURCE_NONE) {
> - dev_warn(match, "No CHBS found for Host Bridge (UID %lld)\n", uid);
> + dev_warn(match, "CHBCR invalid for Host Bridge (UID %lld)\n",
> + uid);
> return 0;
> }
>
>
prev parent reply other threads:[~2022-12-05 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 20:21 [PATCH] cxl/acpi: Warn about an invalid CHBCR in an existing CHBS entry Dan Williams
2022-12-05 21:01 ` Dave Jiang [this message]
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=08d4f315-4c91-225b-d2dd-98ed111ce950@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rrichter@amd.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