From: Ali Alnubani <alialnu@nvidia.com>
To: Chenbo Xia <chenbo.xia@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"probb@iol.unh.edu" <probb@iol.unh.edu>,
"miao.li@intel.com" <miao.li@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Yahui Cao <yahui.cao@intel.com>,
Sunil Kumar Kori <skori@marvell.com>
Subject: RE: [PATCH] bus/pci: fix missing MMIO APIs in Windows
Date: Thu, 8 Jun 2023 08:54:59 +0000 [thread overview]
Message-ID: <DM4PR12MB51678DE09721EA2B12F7CA5DDA50A@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230608074305.38061-1-chenbo.xia@intel.com>
> -----Original Message-----
> From: Chenbo Xia <chenbo.xia@intel.com>
> Sent: Thursday, June 8, 2023 10:43 AM
> To: dev@dpdk.org
> Cc: david.marchand@redhat.com; NBU-Contact-Thomas Monjalon
> (EXTERNAL) <thomas@monjalon.net>; Ali Alnubani <alialnu@nvidia.com>;
> probb@iol.unh.edu; miao.li@intel.com; stable@dpdk.org; Yahui Cao
> <yahui.cao@intel.com>; Sunil Kumar Kori <skori@marvell.com>
> Subject: [PATCH] bus/pci: fix missing MMIO APIs in Windows
>
> MMIO read and write APIs were defined in PCI bus. But the corresponding
> implementations are not done in windows. This patch fixes this.
>
> Bugzilla ID: 1245
> Fixes: 095cf6e68b28 ("bus/pci: introduce MMIO read/write")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
> ---
Resolves the build failure for me, thanks Chenbo.
Tested-by: Ali Alnubani <alialnu@nvidia.com>
next prev parent reply other threads:[~2023-06-08 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 7:43 Chenbo Xia
2023-06-08 8:54 ` Ali Alnubani [this message]
2023-06-08 8:58 ` Xia, Chenbo
2023-06-08 10:04 ` Thomas Monjalon
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=DM4PR12MB51678DE09721EA2B12F7CA5DDA50A@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=miao.li@intel.com \
--cc=probb@iol.unh.edu \
--cc=skori@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yahui.cao@intel.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).