From: Luca Boccassi <bluca@debian.org>
To: "Rastislav Černay" <cernay@netcope.com>,
"Ferruh Yigit" <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] net/nfb: new netcope driver
Date: Mon, 01 Apr 2019 15:23:54 +0100 [thread overview]
Message-ID: <ffe8736cfd886f4f965b6fae46b3df2df32c67fb.camel@debian.org> (raw)
In-Reply-To: <CAGS_BLkFoFwanZyV_h919JMLQsOUUcDVkoKgoogHd7qX5aDFOw@mail.gmail.com>
On Mon, 2019-04-01 at 16:55 +0200, Rastislav Černay wrote:
> Hi Ferruh,
<...>
> btw, why do you prefer to have driver as experimental?
> What does it mean it being experimental from your point of view
> exactly?
> <...>
> I do not prefer to have driver experimental, only reason it is there
> is
> this mail:
>
> Luca Boccassi
> bluca@debian.org
>
> Tue, Mar 5, 11:41 PM
> to me, dev
> <...>
> > diff --git a/drivers/net/nfb/rte_nfb_pmd_version.map
> > b/drivers/net/nfb/rte_nfb_pmd_version.map
> > new file mode 100644
> > index 0000000..97fd251
> > --- /dev/null
> > +++ b/drivers/net/nfb/rte_nfb_pmd_version.map
> > @@ -0,0 +1,4 @@
> > +DPDK_19.02 {
> > +
> > + local: *;
> > +};
>
> These are all new symbols so they should be marked as experimental,
> please see doc/guides/contributing/versioning.rst
>
> So after reading doc/guides/contributing/versioning.rst I thought
> that
> all new drivers should be experimental as they are new before they
> stabilize,
> and during this time changes can be done to public functions without
> much
> hassle.
> Should I keep driver experimental?
Sorry that was just a misunderstanding on my part, I was thinking of
libraries. Please disregard that comment.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-04-01 14:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 12:57 [dpdk-dev] [PATCH] net/nfb: new Netcope driver Rastislav Cernay
2019-02-26 12:57 ` [dpdk-dev] [PATCH] net/nfb: new netcope driver Rastislav Cernay
2019-02-26 14:20 ` Rami Rosen
2019-02-26 16:33 ` Rastislav Černay
2019-02-26 15:46 ` Stephen Hemminger
2019-02-27 11:43 ` [dpdk-dev] [PATCH v2] net/nfb: new Netcope driver Rastislav Cernay
2019-02-27 15:28 ` Ferruh Yigit
2019-03-01 14:37 ` [dpdk-dev] [PATCH v3] net/nfb: new netcope driver Rastislav Cernay
2019-03-01 18:47 ` Stephen Hemminger
2019-03-04 14:07 ` Rastislav Černay
2019-03-01 18:50 ` Stephen Hemminger
2019-03-04 9:53 ` David Marchand
2019-03-04 11:34 ` David Marchand
2019-03-04 14:33 ` Rastislav Černay
2019-03-04 12:35 ` David Marchand
2019-03-04 12:48 ` David Marchand
2019-03-04 15:15 ` Rastislav Černay
2019-03-05 20:31 ` Rami Rosen
2019-03-05 22:41 ` Luca Boccassi
2019-03-06 14:51 ` Rastislav Černay
2019-03-06 13:25 ` Luca Boccassi
2019-03-07 13:24 ` [dpdk-dev] [PATCH v4] " Rastislav Cernay
2019-03-07 13:46 ` Luca Boccassi
2019-03-07 14:14 ` Jan Remeš
2019-03-22 12:12 ` [dpdk-dev] [PATCH v5] " Rastislav Cernay
2019-03-22 12:12 ` Rastislav Cernay
2019-03-28 16:01 ` Ferruh Yigit
2019-03-28 16:01 ` Ferruh Yigit
2019-04-01 14:55 ` Rastislav Černay
2019-04-01 14:22 ` Ferruh Yigit
2019-04-01 14:22 ` Ferruh Yigit
2019-04-02 16:05 ` Rastislav Černay
2019-04-02 16:05 ` Rastislav Černay
2019-04-01 14:23 ` Luca Boccassi [this message]
2019-04-01 14:23 ` Luca Boccassi
2019-04-01 14:55 ` Rastislav Černay
2019-04-04 9:05 ` [dpdk-dev] [PATCH v6] " Rastislav Cernay
2019-04-04 9:05 ` Rastislav Cernay
2019-04-05 0:08 ` Ferruh Yigit
2019-04-05 0:08 ` Ferruh Yigit
2019-04-07 15:03 ` [dpdk-dev] [PATCH v7] " Rastislav Cernay
2019-04-07 15:03 ` Rastislav Cernay
2019-04-12 12:15 ` Ferruh Yigit
2019-04-12 12:15 ` Ferruh Yigit
2019-04-12 12:16 ` Ferruh Yigit
2019-04-12 12:16 ` Ferruh Yigit
2019-04-12 14:37 ` [dpdk-dev] [PATCH] net/nfb: remove redundant linking Rastislav Cernay
2019-04-12 14:37 ` Rastislav Cernay
2019-04-12 15:02 ` Ferruh Yigit
2019-04-12 15:02 ` Ferruh Yigit
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=ffe8736cfd886f4f965b6fae46b3df2df32c67fb.camel@debian.org \
--to=bluca@debian.org \
--cc=cernay@netcope.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).