patches for DPDK stable branches
 help / color / mirror / Atom feed
From: yoursunny <sunnylandh@gmail.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Akhil Goyal <akhil.goyal@nxp.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9
Date: Thu, 1 Nov 2018 07:21:09 -0400	[thread overview]
Message-ID: <CANsAqf6vEcHexqAsWvJ7EcMO_sUcivu07E-FoGnRJQ+fQ5j=SA@mail.gmail.com> (raw)
In-Reply-To: <20181101111121.5570-1-bluca@debian.org>

Hi Luca

I didn't manage to apply following commits from upstream to stable branch
> 16.11: conflict happens. I'm wondering can the authors check the following
> list and backport those patches belong to you?
>
> FYI, branch 16.11 is located at tree:
>    git://dpdk.org/dpdk-stable
>
> f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined
> operation


My commit is irrelevant to DPDK 16.11. I’m fixing a small bug introduced
after DPDK gains asymmetric crypto feature. Back then DPDK does not support
assymetric crypto.

> Yours, Junxiao

  reply	other threads:[~2018-11-01 11:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 16:55 Luca Boccassi
2018-10-03 16:57 ` Luca Boccassi
2018-10-18  8:37 ` Luca Boccassi
2018-11-01 11:11   ` Luca Boccassi
2018-11-01 11:21     ` yoursunny [this message]
2018-11-01 11:25       ` Luca Boccassi
2018-11-02  7:51     ` Phil Yang (Arm Technology China)
2018-11-19 10:56     ` Luca Boccassi
2018-11-26 12:21       ` Luca Boccassi
2018-11-27 12:55         ` Ali Alnubani
2018-11-27 18:49           ` Luca Boccassi
2018-11-28 10:02         ` Luca Boccassi
2018-11-28 10:11           ` Ilya Maximets

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='CANsAqf6vEcHexqAsWvJ7EcMO_sUcivu07E-FoGnRJQ+fQ5j=SA@mail.gmail.com' \
    --to=sunnylandh@gmail.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bluca@debian.org \
    --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).