patches for DPDK stable branches
 help / color / mirror / Atom feed
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-stable] [PATCH 2/3] rawdev: return NUMA socket id to the user
Date: Tue, 7 Jul 2020 13:33:13 +0100
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

  reply	other threads:[~2020-07-07 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200706103132.7691-1-bruce.richardson@intel.com>
2020-07-06 10:31 ` [dpdk-stable] [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   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2020-07-07 12:31     ` Bruce Richardson
2020-07-06 10:31 ` [dpdk-stable] [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   ` Thomas Monjalon
2020-07-07 12:33     ` Bruce Richardson [this message]
2020-07-06 10:31 ` [dpdk-stable] [PATCH 3/3] rawdev: fix missing dump function in map file Bruce Richardson
2020-07-07  3:40   ` Hemant Agrawal

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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git