DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Andy Pei <andy.pei@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, Rosen Xu <rosen.xu@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] bus/ifpga: fix ifpga afu driver probe failure handler
Date: Fri, 18 Jan 2019 20:06:33 +0100	[thread overview]
Message-ID: <17392496.4iuxs547d5@xps> (raw)
In-Reply-To: <20190118111233.45114-1-ferruh.yigit@intel.com>

18/01/2019 12:12, Ferruh Yigit:
> From: Andy Pei <andy.pei@intel.com>
> 
> In the original code, when an AFU device probe a driver,
> if the first driver in the driver list does not support
> this device or some error happens, bus probe returns an error.
> 
> With this patch, a device will try to match driver in the driver
> list one by one until an appropriate driver is found.
> 
> If some error happens, the error is returned. If the current driver
> does not support the device, just try the next driver in the list.
> 
> If all the drivers in the list are tried and no driver matches,
> 0 is returned. Otherwise, the error code is returned.
> 
> Fixes: 05fa3d4a6539 ("bus/ifpga: add Intel FPGA bus library")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Andy Pei <andy.pei@intel.com>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Rosen Xu <rosen.xu@intel.com>

Applied, thanks

      reply	other threads:[~2019-01-18 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  1:40 [dpdk-dev] [DPDK] /driver/bus/ifpga: fix " AndyPei
2019-01-14  5:14 ` Xu, Rosen
2019-01-15  8:38 ` Xu, Rosen
2019-01-17  5:36 ` [dpdk-dev] [DPDK] bus/ifpga: fix ifpga afu " Andy Pei
2019-01-18 11:12   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2019-01-18 19:06     ` Thomas Monjalon [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=17392496.4iuxs547d5@xps \
    --to=thomas@monjalon.net \
    --cc=andy.pei@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=rosen.xu@intel.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).