patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rasesh Mody <rmody@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	 Ferruh Yigit <ferruh.yigit@intel.com>,
	 GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>,
	dpdk stable <stable@dpdk.org>,
	 Shahed Shaikh <shshaikh@marvell.com>,
	Igor Russkikh <irusskikh@marvell.com>
Subject: Re: [dpdk-stable] [EXT] Re: [dpdk-dev] [PATCH] net/qede: fix link state configuration
Date: Thu, 14 May 2020 15:47:43 +0530	[thread overview]
Message-ID: <CALBAE1P2rOo5yJxFJd_LgBBkuET2cedUR98o=bPmaR592u7xVQ@mail.gmail.com> (raw)
In-Reply-To: <BYAPR18MB28385A3A50B834AA540AB8CEB5BF0@BYAPR18MB2838.namprd18.prod.outlook.com>

On Thu, May 14, 2020 at 9:41 AM Rasesh Mody <rmody@marvell.com> wrote:
>
> Hi Jerin,
>
> >From: Jerin Jacob <jerinjacobk@gmail.com>
> >Sent: Wednesday, May 13, 2020 9:25 AM
> >
> >On Tue, May 12, 2020 at 6:16 AM Rasesh Mody <rmody@marvell.com> wrote:
> >>
> >> Move link state enable/disable to dev_start() and dev_stop()
> >> respectively. This will ensure when devices are stopped, link status
> >> will be appropriately shown as down.
> >>
> >> Fixes: dd28bc8c6ef4 ("net/qede: fix VF port creation sequence")
> >
> >I assume you need this patch for -rc3.
> >Please rebase the patch to dpdk-next-net-mrvl and send v2.
>
> Yes, this patch is for -rc3.
> This patch had a dependency on https://patches.dpdk.org/patch/69737/.
> I've submitted a v2 for this patch, please apply.

Applied to dpdk-next-net-mrvl/master. Thanks



>
> Thanks!
> -Rasesh
> >
> >log:
> >git am -3 /tmp/to_merge/net-qede-fix-link-state-configuration
> >
> >Applying: net/qede: fix link state configuration
> >error: sha1 information is lacking or useless
> >(drivers/net/qede/qede_ethdev.c).
> >error: could not build fake ancestor
> >Patch failed at 0001 net/qede: fix link state configuration
> >hint: Use 'git am --show-current-patch=diff' to see the failed patch When you
> >have resolved this problem, run "git am --continue".
> >If you prefer to skip this patch, run "git am --skip" instead.
> >To restore the original branch and stop patching, run "git am --abort".
> >HEAD is now at a8b8a8631 node: fix arm64 build with old gcc git am failed
> >/tmp/g//net-qede-fix-link-state-configuration
> >Wed 13 May 2020 09:51:26 PM IST
> >
> >
> >> Cc: stable@dpdk.org
> >>
> >> Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
> >> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> >> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
> >> ---
> >>  drivers/net/qede/qede_ethdev.c | 14 +++++++++-----
> >>  1 file changed, 9 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/drivers/net/qede/qede_ethdev.c
> >> b/drivers/net/qede/qede_ethdev.c index bcd8252d9..9a5847076 100644
> >> --- a/drivers/net/qede/qede_ethdev.c
> >> +++ b/drivers/net/qede/qede_ethdev.c
> >> @@ -1150,6 +1150,9 @@ static int qede_dev_start(struct rte_eth_dev
> >*eth_dev)
> >>         if (qede_activate_vport(eth_dev, true))
> >>                 goto err;
> >>
> >> +       /* Bring-up the link */
> >> +       qede_dev_set_link_state(eth_dev, true);
> >> +
> >>         /* Update link status */
> >>         qede_link_update(eth_dev, 0);
> >>
> >> @@ -1179,6 +1182,12 @@ static void qede_dev_stop(struct rte_eth_dev
> >*eth_dev)
> >>          */
> >>         qede_assign_rxtx_handlers(eth_dev, true);
> >>
> >> +       /* Bring the link down */
> >> +       qede_dev_set_link_state(eth_dev, false);
> >> +
> >> +       /* Update link status */
> >> +       qede_link_update(eth_dev, 0);
> >> +
> >>         /* Disable vport */
> >>         if (qede_activate_vport(eth_dev, false))
> >>                 return;
> >> @@ -1563,8 +1572,6 @@ static void qede_dev_close(struct rte_eth_dev
> >*eth_dev)
> >>         eth_dev->data->nb_rx_queues = 0;
> >>         eth_dev->data->nb_tx_queues = 0;
> >>
> >> -       /* Bring the link down */
> >> -       qede_dev_set_link_state(eth_dev, false);
> >>         qdev->ops->common->slowpath_stop(edev);
> >>         qdev->ops->common->remove(edev);
> >>         rte_intr_disable(&pci_dev->intr_handle);
> >> @@ -2671,9 +2678,6 @@ static int qede_common_dev_init(struct
> >> rte_eth_dev *eth_dev, bool is_vf)
> >>
> >>         eth_dev->dev_ops = (is_vf) ? &qede_eth_vf_dev_ops :
> >> &qede_eth_dev_ops;
> >>
> >> -       /* Bring-up the link */
> >> -       qede_dev_set_link_state(eth_dev, true);
> >> -
> >>         adapter->num_tx_queues = 0;
> >>         adapter->num_rx_queues = 0;
> >>         SLIST_INIT(&adapter->arfs_info.arfs_list_head);
> >> --
> >> 2.18.0
> >>
>

  reply	other threads:[~2020-05-14 10:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  0:46 [dpdk-stable] " Rasesh Mody
2020-05-13 16:24 ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2020-05-14  4:11   ` [dpdk-stable] [EXT] " Rasesh Mody
2020-05-14 10:17     ` Jerin Jacob [this message]
2020-05-14  4:09 ` [dpdk-stable] [PATCH v2] " 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='CALBAE1P2rOo5yJxFJd_LgBBkuET2cedUR98o=bPmaR592u7xVQ@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=jerinj@marvell.com \
    --cc=rmody@marvell.com \
    --cc=shshaikh@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).