From: Marco Varlese <mvarlese@suse.de>
To: Yongseok Koh <yskoh@mellanox.com>,
"Mody, Rasesh" <Rasesh.Mody@cavium.com>
Cc: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 17.11.4 patches review and test
Date: Thu, 23 Aug 2018 09:43:01 +0200 [thread overview]
Message-ID: <d5e167b85b667883465dc02175ea4a257b36e0c1.camel@suse.de> (raw)
In-Reply-To: <696725fc29b176db285a0fecadfc8a46b5ecdeb2.camel@suse.de>
On Thu, 2018-08-23 at 09:04 +0200, Marco Varlese wrote:
> On Wed, 2018-08-22 at 23:29 +0000, Yongseok Koh wrote:
> > > On Aug 21, 2018, at 12:38 AM, Marco Varlese <mvarlese@suse.de> wrote:
> > >
> > > On Mon, 2018-08-20 at 22:35 +0000, Mody, Rasesh wrote:
> > > > > From: dev <dev-bounces@dpdk.org> On Behalf Of Marco Varlese
> > > > > Sent: Monday, August 20, 2018 2:21 AM
> > > > >
> > > > > Hi,
> > > > >
> > > > > The code in 17.11.4-rc1 does not compile for me.
> > > >
> > > > This needs to be fixed for 17.11.4 as rte_eth_linkstatus_set() is not
> > > > available in DPDK 17.11.x. Will send a patch with fix.
> > >
> > > Please, once a respin for 17.11.4 is available drop me a line and I will
> > > kick
> > > off again the process on my side.
> >
> > Thank you, Rasesh.
> > "net/bnx2x: fix to set device link status" has been applied to stable/17.11
> >
> > Marco, can you please retest it?
>
> Can you please create a new tarball as -rc2?
Never mind: I applied the incremental patch on top of the -rc1 tarball.
Things look good now.
Just do not forget to apply the patch to the 17.11 repo before tagging again. :)
> >
> > I'll postpone the GA schedule, which was planned on this Friday.
> >
> > Yongseok
> >
[SNIP]
Cheers,
Marco
next prev parent reply other threads:[~2018-08-23 7:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 18:18 Yongseok Koh
2018-08-20 9:21 ` Marco Varlese
2018-08-20 22:35 ` Mody, Rasesh
2018-08-21 7:38 ` Marco Varlese
2018-08-22 23:29 ` Yongseok Koh
2018-08-23 7:04 ` Marco Varlese
2018-08-23 7:43 ` Marco Varlese [this message]
2018-08-21 10:07 ` Alejandro Lucero
2018-08-23 0:19 ` Yongseok Koh
2018-08-23 1:23 ` Yongseok Koh
2018-08-23 11:29 ` Thomas Monjalon
2018-08-23 16:18 ` Yongseok Koh
2018-08-24 8:51 ` Alejandro Lucero
2018-08-24 14:31 ` Yongseok Koh
2018-08-24 15:00 ` Alejandro Lucero
2018-08-24 15:10 ` Yongseok Koh
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=d5e167b85b667883465dc02175ea4a257b36e0c1.camel@suse.de \
--to=mvarlese@suse.de \
--cc=Rasesh.Mody@cavium.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.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).