patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-stable] [PATCH] crypto/scheduler: fix slave init attach
Date: Wed, 19 Apr 2017 16:07:07 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974780CAF5@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8974780CAD6@IRSMSX108.ger.corp.intel.com>



> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of De Lara
> Guarch, Pablo
> Sent: Wednesday, April 19, 2017 5:04 PM
> To: Zhang, Roy Fan; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: Re: [dpdk-stable] [PATCH] crypto/scheduler: fix slave init attach
> 
> 
> 
> > -----Original Message-----
> > From: Zhang, Roy Fan
> > Sent: Wednesday, April 19, 2017 2:42 PM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo; stable@dpdk.com
> > Subject: [PATCH] crypto/scheduler: fix slave init attach
> >
> > Fixes: 881851676940 ("crypto/scheduler: improve commandline
> parsing")
> >
> > This patch fix the slaves attaching initially.
> >
> > Originally, the scheduler will try to attach the slaves passed by the
> > cmdline option in the initial stage, this may break the sequence
> > of the slaves inside the scheduler.
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> 
> Squashed into the affected commit in the subtree.
> 
> Thanks,
> Pablo

Forgot to mention that this DOES NOT have to go into the stable branch,
as it is a fix for a commit sent in this release.

Thanks,
Pablo

      reply	other threads:[~2017-04-19 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1492609337-44733-1-git-send-email-roy.fan.zhang@intel.com>
2017-04-19 16:04 ` De Lara Guarch, Pablo
2017-04-19 16:07   ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D8974780CAF5@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@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).