[dpdk-dev] version: 18.05-rc0
Checks
Commit Message
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
lib/librte_eal/common/include/rte_version.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Comments
The new release cycle is started!
If you think some patches are already ready for integration in master,
please notify me.
Note that changes impacting a lot of future patches (big changes, renames,
or core features) are preferred to be integrated early in the cycle.
Thanks for your attention
Hi Thomas,
Can you integrate ?
http://dpdk.org/dev/patchwork/patch/33666/
An early integration will help the subsequent kernel module patches to use new path.
Regards,
Hemant
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, February 20, 2018 2:34 AM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] version: 18.05-rc0
>
> The new release cycle is started!
>
> If you think some patches are already ready for integration in master, please
> notify me.
>
> Note that changes impacting a lot of future patches (big changes, renames, or
> core features) are preferred to be integrated early in the cycle.
>
> Thanks for your attention
On Tue, Feb 20, 2018 at 06:12:49AM +0000, Hemant Agrawal wrote:
> Hi Thomas,
> Can you integrate ?
> http://dpdk.org/dev/patchwork/patch/33666/
>
> An early integration will help the subsequent kernel module patches to use new path.
>
> Regards,
> Hemant
>
I think that could do with a respin to include the meson.build file
changes also.
/Bruce
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Tuesday, February 20, 2018 2:34 AM
> > To: dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH] version: 18.05-rc0
> >
> > The new release cycle is started!
> >
> > If you think some patches are already ready for integration in master, please
> > notify me.
> >
> > Note that changes impacting a lot of future patches (big changes, renames, or
> > core features) are preferred to be integrated early in the cycle.
> >
> > Thanks for your attention
On 19-Feb-18 9:03 PM, Thomas Monjalon wrote:
> The new release cycle is started!
>
> If you think some patches are already ready for integration in master,
> please notify me.
>
> Note that changes impacting a lot of future patches (big changes, renames,
> or core features) are preferred to be integrated early in the cycle.
>
> Thanks for your attention
>
Hi Thomas,
http://dpdk.org/dev/patchwork/patch/35043/
Would be great to get this reviewed and integrated ahead of memory
rework v1, as it will depend on this patch (among other things).
Deprecation notice for this patch was integrated in previous release:
http://dpdk.org/dev/patchwork/patch/33853/
Hi Bruce,
> On Tue, Feb 20, 2018 at 06:12:49AM +0000, Hemant Agrawal wrote:
> > Hi Thomas,
> > Can you integrate ?
> >
> > An early integration will help the subsequent kernel module patches to use
> new path.
> >
> > Regards,
> > Hemant
> >
>
> I think that could do with a respin to include the meson.build file changes also.
>
[Hemant] I have just sent a v6. However,
I was only able to test linux based igb_uio.ko compilation with meson.
I could not find the kni build support with meson.
My freebsd meson compilation is failing. Will you please help in checking out the freebsd meson changes?
Regards,
Hemant
> /Bruce
>
On Wed, Feb 21, 2018 at 08:16:07AM +0000, Hemant Agrawal wrote:
> Hi Bruce,
>
>
> > On Tue, Feb 20, 2018 at 06:12:49AM +0000, Hemant Agrawal wrote:
> > > Hi Thomas,
> > > Can you integrate ?
> > >
> > > An early integration will help the subsequent kernel module patches to use
> > new path.
> > >
> > > Regards,
> > > Hemant
> > >
> >
> > I think that could do with a respin to include the meson.build file changes also.
> >
> [Hemant] I have just sent a v6. However,
> I was only able to test linux based igb_uio.ko compilation with meson.
> I could not find the kni build support with meson.
Yes, it's not implemented yet.
>
> My freebsd meson compilation is failing. Will you please help in checking out the freebsd meson changes?
Yes, will do.
/Bruce
@@ -32,7 +32,7 @@ extern "C" {
/**
* Minor version/month number i.e. the mm in yy.mm.z
*/
-#define RTE_VER_MONTH 02
+#define RTE_VER_MONTH 05
/**
* Patch level number i.e. the z in yy.mm.z
@@ -42,14 +42,14 @@ extern "C" {
/**
* Extra string to be appended to version number
*/
-#define RTE_VER_SUFFIX ""
+#define RTE_VER_SUFFIX "-rc"
/**
* Patch release number
* 0-15 = release candidates
* 16 = release
*/
-#define RTE_VER_RELEASE 16
+#define RTE_VER_RELEASE 0
/**
* Macro to compute a version number usable for comparisons