From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Jan Remeš" <remes@netcope.com>
Cc: Rastislav Cernay <cernay@netcope.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/szedata2: add Silicom Mango support
Date: Fri, 28 Jun 2019 16:35:54 +0100 [thread overview]
Message-ID: <6ae364a4-6e43-ed57-7d67-bdbb904cd41a@intel.com> (raw)
In-Reply-To: <CAAnEdtCd+1+LgHojGGZD3p15i6bj1MBdcKN7NuMMEMqEVhNFKw@mail.gmail.com>
On 6/28/2019 3:08 PM, Jan Remeš wrote:
> On Thu, Jun 27, 2019 at 7:49 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>>
>> On 6/13/2019 2:01 PM, Rastislav Cernay wrote:
>>> From: Rastislav Cernay <cernay@netcope.com>
>>>
>>> Add support for Silicom FB2CGG3 smart NIC
>>>
>>> Signed-off-by: Rastislav Cernay <cernay@netcope.com>
>>
>> Applied to dpdk-next-net/master, thanks.
>>
>> (But this requires Ack from maintainer, Jan if you agree please ack the patch,
>> or I will drop from the tree)
>>
>>
>> Similar to nfb, is this requires any release notes or web update, because of the
>> new device support? If so please send the them. I can squash doc path later.
>>
>
> Acked-by: Jan Remes <remes@netcope.com>
I will add the ack to the commit in next-net
>
> We should cover in the documentation, which cards are supported. I
> have talked to Rasto and he will send a subsequent patch for the
> documentation, addressing both our PMDs.
I will wait for this patch to squash into existing one, thanks.
>
> Also, he and I will co-maintain both "szedata2" and "nfb" PMDs - I
> will send a patch for the MAINTAINERS file.
>
> BR,
> Jan
>
next prev parent reply other threads:[~2019-06-28 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 13:01 Rastislav Cernay
2019-06-27 17:49 ` Ferruh Yigit
2019-06-28 14:08 ` Jan Remeš
2019-06-28 15:35 ` Ferruh Yigit [this message]
2019-07-01 13:12 ` Rastislav Černay
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=6ae364a4-6e43-ed57-7d67-bdbb904cd41a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cernay@netcope.com \
--cc=dev@dpdk.org \
--cc=remes@netcope.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).