From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Solarflare PMD submission question
Date: Fri, 28 Oct 2016 15:14:20 +0200 [thread overview]
Message-ID: <4082712.Wtfd7g8Mk6@xps13> (raw)
In-Reply-To: <4e5189f0-d340-ae7c-0300-aefd64041022@solarflare.com>
2016-10-28 16:05, Andrew Rybchenko:
> On 10/28/2016 03:33 PM, Thomas Monjalon wrote:
> > 2016-10-28 13:50, Andrew Rybchenko:
> >> First of all I'd like to double check that it is clear that we discuss
> >> libefx
> >> (base driver in terms of DPDK) import here. The PMD itself is already split
> >> in 20+ patches.
> > I don't know libefx. In DPDK, a base driver is often a subdirectory
> > inside the PMD. Will it be the case?
>
> Yes. Just to be absolutely sure: are the discussed requirements to split
> applicable to base driver import?
Yes I'm talking about the base driver. But they are not some requirements.
Take them as advices.
The first priority is to welcome your new driver.
The second priority is to make sure that it is open and readable enough.
next prev parent reply other threads:[~2016-10-28 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 6:34 Andrew Rybchenko
2016-10-27 10:37 ` Thomas Monjalon
2016-10-28 10:50 ` Andrew Rybchenko
2016-10-28 12:33 ` Thomas Monjalon
2016-10-28 13:05 ` Andrew Rybchenko
2016-10-28 13:14 ` Thomas Monjalon [this message]
2016-10-28 14:43 ` Andrew Rybchenko
2016-11-18 16:50 ` Andrew Rybchenko
2016-11-21 8:19 ` Thomas Monjalon
2016-11-21 8:46 ` Andrew Rybchenko
2016-11-21 8:59 ` Thomas Monjalon
2016-11-21 10:30 ` Ferruh Yigit
2016-11-21 15:03 ` Andrew Rybchenko
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=4082712.Wtfd7g8Mk6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@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).