DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Radha Mohan Chintakuntla <radhac@marvell.com>
Cc: vburru@marvell.com, dev@dpdk.org, stable@dpdk.org, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2] raw/octeontx2_dma: fix unavailable PCI device in dpivf
Date: Thu, 15 Apr 2021 16:43:16 +0200	[thread overview]
Message-ID: <2586651.Fnn1RPQ0FD@thomas> (raw)
In-Reply-To: <20210409080627.123195-1-radhac@marvell.com>

09/04/2021 10:06, Radha Mohan Chintakuntla:
> The PCI device address is being used for sending mailbox which was
> introduced in previous commit which replaced the macros so that
> multiple DPI blocks in the hardware can be supported.

The sentence is too long and complex.
My advice: make multiple short sentences.

> This patch fixes a NULL pointer access by assigning the PCI device
> structure to dpivf.
> Fixes: 4495bd887d38 ("raw/octeontx2_dma: support multiple DPI blocks")
Cc: stable@dpdk.org

> Signed-off-by: Radha Mohan Chintakuntla <radhac@marvell.com>

Applied with title "raw/octeontx2_dma: assign PCI device in DPI VF"

      reply	other threads:[~2021-04-15 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  8:06 Radha Mohan Chintakuntla
2021-04-15 14:43 ` Thomas Monjalon [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2586651.Fnn1RPQ0FD@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=radhac@marvell.com \
    --cc=stable@dpdk.org \
    --cc=vburru@marvell.com \


* 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).