From: "Gupta, Nipun" <Nipun.Gupta@amd.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Agarwal, Nikhil" <nikhil.agarwal@amd.com>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>
Subject: RE: [PATCH] bus/cdx: silence bus scan when CDX is unavailable
Date: Fri, 9 Jun 2023 11:14:09 +0000 [thread overview]
Message-ID: <CH3PR12MB830813DC8F782D661F207C80E851A@CH3PR12MB8308.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230609111109.2877000-1-david.marchand@redhat.com>
[Public]
Acked-by: Nipun Gupta <nipun.gupta@amd.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Friday, June 9, 2023 4:41 PM
> To: dev@dpdk.org
> Cc: Gupta, Nipun <Nipun.Gupta@amd.com>; Agarwal, Nikhil
> <nikhil.agarwal@amd.com>; Yigit, Ferruh <Ferruh.Yigit@amd.com>
> Subject: [PATCH] bus/cdx: silence bus scan when CDX is unavailable
>
> Absence of the CDX bus is not an error.
>
> Bugzilla ID: 1246
> Fixes: 45ef232af515 ("bus/cdx: introduce AMD CDX bus")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/cdx/cdx.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bus/cdx/cdx.c b/drivers/bus/cdx/cdx.c
> index 9607096d18..28bbf92ed5 100644
> --- a/drivers/bus/cdx/cdx.c
> +++ b/drivers/bus/cdx/cdx.c
> @@ -268,9 +268,9 @@ cdx_scan(void)
>
> dir = opendir(RTE_CDX_BUS_DEVICES_PATH);
> if (dir == NULL) {
> - CDX_BUS_ERR("%s(): opendir failed: %s", __func__,
> + CDX_BUS_INFO("%s(): opendir failed: %s", __func__,
> strerror(errno));
> - return -1;
> + return 0;
> }
>
> while ((e = readdir(dir)) != NULL) {
> --
> 2.40.1
next prev parent reply other threads:[~2023-06-09 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:11 David Marchand
2023-06-09 11:14 ` Gupta, Nipun [this message]
2023-06-09 13:20 ` David Marchand
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=CH3PR12MB830813DC8F782D661F207C80E851A@CH3PR12MB8308.namprd12.prod.outlook.com \
--to=nipun.gupta@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nikhil.agarwal@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;
as well as URLs for NNTP newsgroup(s).