DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v1 0/2] baseband/fpga_lte_fec: bug fixes from HW validation
Date: Tue, 22 Oct 2019 07:58:34 +0000	[thread overview]
Message-ID: <VE1PR04MB663918F7FDF2FAD5340F96EFE6680@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1571685850-382423-1-git-send-email-nicolas.chautru@intel.com>


> 
> Failures found when running validation with FPGA HW and the related FPGA PMD
> driver on latest code base pre 19.11.
> Two bug fixes below :
> - The first error is a fatal failure during probing which was missed and would
> fundamentally prevent using the driver. This was missed as HW validation was
> still focus on old DPDK release. The assumptions had change on driver
> assignment during probing and the impact was missed so far.
> - The 2nd failure is not as critical but good to fix as it can cause spurrious
> detection of flushing failure.
> (Resending as previous one did not seem to go through on dpdk ml).
> 
> Nic Chautru (2):
>   baseband/fpga_lte_fec: fix probing fatal failure
>   baseband/fpga_lte_fec: fix to polling of MMIO register
> 
>  drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
Add Bugzilla id if available.
Missing fixes line in both of your patches.
Also add cc:stable

Regards,
Akhil

      parent reply	other threads:[~2019-10-22  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 19:24 Nicolas Chautru
2019-10-21 19:24 ` [dpdk-dev] [PATCH v1 1/2] baseband/fpga_lte_fec: fix probing fatal failure Nicolas Chautru
2019-10-21 19:24 ` [dpdk-dev] [PATCH v1 2/2] baseband/fpga_lte_fec: fix to polling of MMIO register Nicolas Chautru
2019-10-22  7:58 ` Akhil Goyal [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=VE1PR04MB663918F7FDF2FAD5340F96EFE6680@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nicolas.chautru@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).