From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rasesh Mody <rmody@marvell.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>,
Igor Russkikh <irusskikh@marvell.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/qede: fix get link details
Date: Sun, 4 Oct 2020 14:07:37 +0530 [thread overview]
Message-ID: <CALBAE1NE2dbaNqHFtPRBuGG_68fL3HiOEr13jgUEHDXk-ntReA@mail.gmail.com> (raw)
In-Reply-To: <20201002195945.20343-1-rmody@marvell.com>
On Sat, Oct 3, 2020 at 1:30 AM Rasesh Mody <rmody@marvell.com> wrote:
>
> This patch fixes get current link details, without this change the link
> details can be inaccurate if proper lock is not acquired.
>
> Fixes: 739a5b2f2b49 ("net/qede/base: use passed ptt handler")
> Cc: stable@dpdk.org
>
> Reported-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
Applied to dpdk-next-net-mrvl/main. Thanks
> ---
> drivers/net/qede/qede_main.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/qede/qede_main.c b/drivers/net/qede/qede_main.c
> index aecb98261..1ae10d99d 100644
> --- a/drivers/net/qede/qede_main.c
> +++ b/drivers/net/qede/qede_main.c
> @@ -584,13 +584,12 @@ qed_get_current_link(struct ecore_dev *edev, struct qed_link_output *if_link)
> hwfn = &edev->hwfns[0];
> if (IS_PF(edev)) {
> ptt = ecore_ptt_acquire(hwfn);
> - if (!ptt)
> - DP_NOTICE(hwfn, true, "Failed to fill link; No PTT\n");
> -
> + if (ptt) {
> qed_fill_link(hwfn, ptt, if_link);
> -
> - if (ptt)
> ecore_ptt_release(hwfn, ptt);
> + } else {
> + DP_NOTICE(hwfn, true, "Failed to fill link; No PTT\n");
> + }
> } else {
> qed_fill_link(hwfn, NULL, if_link);
> }
> --
> 2.18.1
>
next prev parent reply other threads:[~2020-10-04 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 22:41 [dpdk-dev] [PATCH] " Rasesh Mody
2020-10-02 19:59 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2020-10-04 8:37 ` Jerin Jacob [this message]
2020-10-02 20:02 ` [dpdk-dev] [PATCH] " Rasesh Mody
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=CALBAE1NE2dbaNqHFtPRBuGG_68fL3HiOEr13jgUEHDXk-ntReA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=irusskikh@marvell.com \
--cc=rmody@marvell.com \
--cc=stable@dpdk.org \
/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).