From: "Phil Yang (Arm Technology China)" <Phil.Yang@arm.com>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: Akhil Goyal <akhil.goyal@nxp.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Junxiao Shi <git@mail1.yoursunny.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Natalie Samsonov <nsamsono@marvell.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
Tianfei Zhang <tianfei.zhang@intel.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Yelena Krivosheev <yelena@marvell.com>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9
Date: Fri, 2 Nov 2018 07:51:32 +0000 [thread overview]
Message-ID: <DB7PR08MB338556CA26E127EF40E9A546E9CF0@DB7PR08MB3385.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20181101111121.5570-1-bluca@debian.org>
Hi Luca,
I have done my part. Please check it. Thanks!
Thanks,
Phil Yang
> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Thursday, November 1, 2018 7:11 PM
> To: dpdk stable <stable@dpdk.org>
> Cc: Akhil Goyal <akhil.goyal@nxp.com>; Alejandro Lucero
> <alejandro.lucero@netronome.com>; Anatoly Burakov
> <anatoly.burakov@intel.com>; Andrew Rybchenko
> <arybchenko@solarflare.com>; Gavin Hu (Arm Technology China)
> <Gavin.Hu@arm.com>; Jerin Jacob <jerin.jacob@caviumnetworks.com>;
> Junxiao Shi <git@mail1.yoursunny.com>; Konstantin Ananyev
> <konstantin.ananyev@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>; Maxime Coquelin
> <maxime.coquelin@redhat.com>; Natalie Samsonov
> <nsamsono@marvell.com>; Phil Yang (Arm Technology China)
> <Phil.Yang@arm.com>; Shreyansh Jain <shreyansh.jain@nxp.com>; Tianfei
> Zhang <tianfei.zhang@intel.com>; Tiwei Bie <tiwei.bie@intel.com>; Yelena
> Krivosheev <yelena@marvell.com>
> Subject: please help backporting some patches to LTS release 16.11.9
>
> Hi commit authors (and maintainers),
>
> 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
>
> It'd be great if you could do that in one or two weeks. Also, please add a
> heading line like below before the commit log body:
> [ backported from upstream commit xxx ]
>
> Example: http://dpdk.org/browse/dpdk-
> stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
>
> Also please mention the target LTS in the subject line, as we have more than one
> at the same time, for example:
>
> [PATCH 16.11] foo/bar: fix baz
>
> With git send-email, this can be achieved by appending the parameter:
>
> --subject-prefix='16.11'
>
> Please let me know if you have any comments, say, need more time, or it's
> worthless to packport it. And please send it to "stable@dpdk.org", but not
> "dev@dpdk.org".
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 630deed61 Alejandro Lucero bus/pci: compare kernel driver instead of interrupt
> handler
> c23e46594 Jerin Jacob mbuf: fix offload flag name and list
> f49d7e9a9 Junxiao Shi cryptodev: fix pool element size for undefined
> operation
> effdb8bbb Phil Yang app/testpmd: fix physical port socket initialization
> 298413364 Phil Yang app/testpmd: fix vdev socket initialization
> a569af248 Phil Yang app/testpmd: reserve NUMA node per port and per
> ring
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2018-11-02 7:51 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
2018-11-01 11:25 ` Luca Boccassi
2018-11-02 7:51 ` Phil Yang (Arm Technology China) [this message]
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=DB7PR08MB338556CA26E127EF40E9A546E9CF0@DB7PR08MB3385.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=akhil.goyal@nxp.com \
--cc=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bluca@debian.org \
--cc=git@mail1.yoursunny.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nsamsono@marvell.com \
--cc=shreyansh.jain@nxp.com \
--cc=stable@dpdk.org \
--cc=tianfei.zhang@intel.com \
--cc=tiwei.bie@intel.com \
--cc=yelena@marvell.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).