patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "Chen, Junjie J" <junjie.j.chen@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.7
Date: Tue, 08 May 2018 10:50:35 +0100	[thread overview]
Message-ID: <1525773035.23337.78.camel@debian.org> (raw)
In-Reply-To: <AA85A5A5E706C44BACB0BEFD5AC08BF6313F811C@SHSMSX101.ccr.corp.intel.com>

On Mon, 2018-05-07 at 02:08 +0000, Chen, Junjie J wrote:
> The following two patches should be not applicable to 16.11 LTS due
> to lots of rebase work needed.
> 
> 30a701a53  Junjie Chen      net/vhost: fix crash when creating vdev
> dynamically
> e6722dee5  Junjie Chen      net/vhost: fix invalid state
> 
> Cheers
> JJ

Ok, thanks for the heads-up.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-05-08  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 10:49 luca.boccassi
2018-05-07  2:08 ` Chen, Junjie J
2018-05-08  9:50   ` Luca Boccassi [this message]
2018-05-18  9:47 ` luca.boccassi
2018-05-18 12:15   ` [dpdk-stable] [PATCH 0/4] 16.11 Requested backports Andy Green
2018-05-18 12:16     ` [dpdk-stable] [PATCH 1/4] eal: support strlcpy function Andy Green
2018-05-18 12:16     ` [dpdk-stable] [PATCH 2/4] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 12:16     ` [dpdk-stable] [PATCH 3/4] net/qede: fix strncpy Andy Green
2018-05-18 12:16     ` [dpdk-stable] [PATCH 4/4] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 12:48     ` [dpdk-stable] [PATCH 0/4] 16.11 Requested backports Luca Boccassi
2018-05-25 17:24   ` [dpdk-stable] please help backporting some patches to LTS release 16.11.7 luca.boccassi
2018-05-29 21:59     ` Shaikh, Shahed
2018-05-29 22:55       ` Luca Boccassi

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=1525773035.23337.78.camel@debian.org \
    --to=bluca@debian.org \
    --cc=junjie.j.chen@intel.com \
    --cc=stable@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).