From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Gagandeep Singh <G.Singh@nxp.com>,
Thierry Herbelot <thierry.herbelot@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/pfe: no need to check dev to be NULL Pointer
Date: Tue, 29 Jun 2021 11:27:51 +0300 [thread overview]
Message-ID: <1a8a0229-bf72-9b9e-5790-119f001ed320@oktetlabs.ru> (raw)
In-Reply-To: <VI1PR04MB69603FBF75D0370F615A8BF5E1269@VI1PR04MB6960.eurprd04.prod.outlook.com>
On 5/24/21 1:28 PM, Gagandeep Singh wrote:
>
>
>> -----Original Message-----
>> From: Thierry Herbelot <thierry.herbelot@6wind.com>
>> Sent: Monday, May 24, 2021 3:08 PM
>> To: dev@dpdk.org
>> Cc: Thierry Herbelot <thierry.herbelot@6wind.com>; Thomas Monjalon
>> <thomas@monjalon.net>; stable@dpdk.org; Gagandeep Singh
>> <G.Singh@nxp.com>
>> Subject: [PATCH v2] net/pfe: no need to check dev to be NULL Pointer
>>
>> librte_ethdev library is already doing some checks on dev before calling
>> the link update.
>>
>> Fixes: acd4818ea2a45 ("net/pfe: add link status update")
>> Cc: stable@dpdk.org
>> Cc: Gagandeep Singh <g.singh@nxp.com>
>>
>> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
>> --
>> V2: rework after noting dev cannot be NULL
>> ---
>
> Acked-by: Gagandeep Singh <G.singh@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2021-06-29 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 8:59 [dpdk-stable] [PATCH] net/pfe: do not use a possibly " Thierry Herbelot
2021-05-24 9:25 ` Gagandeep Singh
2021-05-24 9:37 ` [dpdk-stable] [PATCH v2] net/pfe: no need to check dev to be " Thierry Herbelot
2021-05-24 10:28 ` Gagandeep Singh
2021-06-29 8:27 ` Andrew Rybchenko [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:
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=1a8a0229-bf72-9b9e-5790-119f001ed320@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.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).