From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Andy Pei <andy.pei@intel.com>
Cc: dev@dpdk.org, Rosen Xu <rosen.xu@intel.com>,
stable@dpdk.org, tianfei.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] bus/ifpga: fix forcing optional devargs
Date: Fri, 18 Jan 2019 20:02:48 +0100 [thread overview]
Message-ID: <12285483.1N2ufjP8Av@xps> (raw)
In-Reply-To: <20190118110701.41625-1-ferruh.yigit@intel.com>
18/01/2019 12:07, Ferruh Yigit:
> From: Andy Pei <andy.pei@intel.com>
>
> Original driver requires users to input "afu_bts" args.
> But driver can also work without an explicit "afu_bts" args.
>
> Fixes: 05fa3d4a6539 ("bus/ifpga: add Intel FPGA bus library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Andy Pei <andy.pei@intel.com>
> Acked-by: Rosen Xu <rosen.xu@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-18 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 1:41 [dpdk-dev] [DPDK] /driver/bus/ifpga: users do not have to input afu_bts in cmdline AndyPei
2019-01-14 5:14 ` Xu, Rosen
2019-01-18 11:07 ` [dpdk-dev] [PATCH v2] bus/ifpga: fix forcing optional devargs Ferruh Yigit
2019-01-18 19:02 ` 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=12285483.1N2ufjP8Av@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 \
--cc=tianfei.zhang@intel.com \
/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).