From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ranjit.menon@intel.com" <ranjit.menon@intel.com>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"Narcisa.Vasile@microsoft.com" <Narcisa.Vasile@microsoft.com>,
Tal Shnaiderman <talshn@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v2] bus/pci: fix probing for non-netuio bound devices
Date: Wed, 17 Mar 2021 09:41:59 -0700 [thread overview]
Message-ID: <40a45d9a-3820-c62d-9822-7c6e4d6f0534@intel.com> (raw)
In-Reply-To: <14301035.AEHYvxyzpe@thomas>
On 3/16/2021 4:20 AM, Thomas Monjalon wrote:
>>> Implement rte_pci_map_device() to distinguish between the devices bound
>>> to netuio and NDIS devices.
>>> Only return success for the netuio devices.
>>>
>>> v2 changes:
>>> - Extended the comment to mention about mapping
>>> - replaced the return errno value with -1
> The changelog should be below the line "---"
> so it is skipped when applying the patch.
Thanks, Thomas. Will keep this in mind.
>
> Missing 'Fixes' tag:
> Fixes: c76ec01b4591 ("bus/pci: support netuio on Windows")
> Cc: stable@dpdk.org
>
>>> Suggested-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>>> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
>>> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
>> Acked-by: Tal Shnaiderman <talshn@nvidia.com>
> Applied, thanks
>
>
next prev parent reply other threads:[~2021-03-17 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 1:40 [dpdk-dev] [PATCH] " Pallavi Kadam
2021-02-10 6:00 ` Tal Shnaiderman
2021-02-10 20:47 ` Kadam, Pallavi
2021-02-10 20:36 ` [dpdk-dev] [PATCH v2] " Pallavi Kadam
2021-02-11 19:30 ` Tal Shnaiderman
2021-03-16 11:20 ` Thomas Monjalon
2021-03-17 16:41 ` Kadam, Pallavi [this message]
2021-03-05 2:04 ` Narcisa Ana Maria Vasile
2021-03-05 2:02 ` [dpdk-dev] [PATCH] " Narcisa Ana Maria Vasile
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=40a45d9a-3820-c62d-9822-7c6e4d6f0534@intel.com \
--to=pallavi.kadam@intel.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@nvidia.com \
--cc=thomas@monjalon.net \
/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).