DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit
Date: Sat, 5 Aug 2017 05:59:05 +0000	[thread overview]
Message-ID: <BLUPR0701MB739082E15382C0421F6B70E9FB70@BLUPR0701MB739.namprd07.prod.outlook.com> (raw)
In-Reply-To: <d2cfd579-3167-4e58-539b-8bc6cc5ea12e@intel.com>

> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Monday, July 31, 2017 10:53 AM
> To: Mody, Rasesh <Rasesh.Mody@cavium.com>; dev@dpdk.org
> Cc: Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>; Thomas
> Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from
> previous ungraceful exit
> 
> On 7/24/2017 11:19 AM, Rasesh Mody wrote:
> > This patch modifies the recovery flow to allow ongoing PCIe
> > transactions to be completed. To achieve this, the load sequence is
> > changed such that the "final_cleanup" notification is sent while the
> > FID_enable is cleared.
> > This change ensures that the chip cleanup actions takes place from
> > previous driver instance if needed.
> >
> > Fixes: ec94dbc57362 ("qede: add base driver")
> >
> > Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
> 
> Series applied to dpdk-next-net/master, thanks.
> 
> Except from patch 5/7, which Shahed Shaikh adds him as one of the driver
> maintainers.
> 
> This is the first patch from "Shahed Shaikh", before getting this patch, I
> believe it is good to have explicit Acks from existing maintainers.
> 
> And this is the process issue, not something that will effect the code, so it can
> be merged in next release or directly to main tree later by Thomas.

Thanks Ferruh!

I have explicitly acked the patch adding Shaded to list of QEDE PMD maintainers.

Thomas,

Could you include the maintainer's patch?

Thanks!
-Rasesh


      reply	other threads:[~2017-08-05  5:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 10:19 Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 2/7] net/qede: fix incorrect queue id for 100G Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 3/7] net/qede/base: fix for adapter specific stats Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 4/7] net/qede: fix inner L3/L4 chksum offload for tunnel frames Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 5/7] doc: list NPAR as supported feature in qede Rasesh Mody
2017-07-28 15:56   ` Mcnamara, John
2017-08-05  5:56   ` Mody, Rasesh
2017-08-06 10:43     ` Thomas Monjalon
2017-07-24 10:19 ` [dpdk-dev] [PATCH 6/7] net/qede: fix chip details print Rasesh Mody
2017-07-24 10:19 ` [dpdk-dev] [PATCH 7/7] net/qede: update PMD version 2.5.2.1 Rasesh Mody
2017-07-31 17:53 ` [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit Ferruh Yigit
2017-08-05  5:59   ` Mody, Rasesh [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=BLUPR0701MB739082E15382C0421F6B70E9FB70@BLUPR0701MB739.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).