From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: nipun.gupta@nxp.com, hemant.agrawal@nxp.com, dev@dpdk.org,
stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 2/3] rawdev: return NUMA socket id to the user
Date: Tue, 7 Jul 2020 13:33:13 +0100 [thread overview]
Message-ID: <20200707123313.GB651@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <2153624.PyFq22NkSC@thomas>
On Tue, Jul 07, 2020 at 02:23:04PM +0200, Thomas Monjalon wrote:
> 06/07/2020 12:31, Bruce Richardson:
> > The rawdev info struct has a socket_id field which was not filled in.
> >
> > We can also omit the checks for the parameter struct being null, since
> > that is previously checked in the function.
> >
> > Cc: stable@dpdk.org
>
> It looks to be a fix.
> Which commit introduced this bug? The original one?
> Fixes: c88b3f2558ed ("rawdev: introduce raw device library")
>
Yes, it can be viewed as a fix and that is the commit introducing the
issue.
/Bruce
next prev parent reply other threads:[~2020-07-07 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:31 [dpdk-dev] [PATCH 0/3] Minor rawdev fixes and enhancements Bruce Richardson
2020-07-06 10:31 ` [dpdk-dev] [PATCH 1/3] rawdev: allow calling info function for unknown rawdevs Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 12:18 ` Thomas Monjalon
2020-07-07 12:31 ` Bruce Richardson
2020-07-06 10:31 ` [dpdk-dev] [PATCH 2/3] rawdev: return NUMA socket id to the user Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 12:23 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2020-07-07 12:33 ` Bruce Richardson [this message]
2020-07-06 10:31 ` [dpdk-dev] [PATCH 3/3] rawdev: fix missing dump function in map file Bruce Richardson
2020-07-07 3:40 ` Hemant Agrawal
2020-07-07 17:17 ` [dpdk-dev] [PATCH 0/3] Minor rawdev fixes and enhancements 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=20200707123313.GB651@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@dpdk.org \
--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).