DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
	James Hershaw <james.hershaw@corigine.com>,
	stable@dpdk.org, Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/nfp: fix incorrect link status after LSC event
Date: Fri, 9 Jun 2023 15:17:37 +0100	[thread overview]
Message-ID: <d9927dc8-5e26-3e92-310a-29d309c78953@amd.com> (raw)
In-Reply-To: <20230609062846.1334539-1-chaoyong.he@corigine.com>

On 6/9/2023 7:28 AM, Chaoyong He wrote:
> From: James Hershaw <james.hershaw@corigine.com>
> 
> Incorrect port speed shown after a link state and interrupt of type
> RTE_ETH_EVENT_INTR_LSC occurs. This is because the interrupt handler for
> this type of event in the nfp PMD does not reconfigure the netdev.
> 
> Fixed by moving the call to the nfp_net_notify_port_speed() function to
> within the nfp_net_link_update() function, which is called by the
> interrupt handler.
> 
> Fixes: 36a9abd4b679 ("net/nfp: write link speed to control BAR")
> Cc: stable@dpdk.org
> 
> Signed-off-by: James Hershaw <james.hershaw@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
>

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2023-06-09 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  6:28 Chaoyong He
2023-06-09 14:17 ` Ferruh Yigit [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=d9927dc8-5e26-3e92-310a-29d309c78953@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=james.hershaw@corigine.com \
    --cc=long.wu@corigine.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.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).