From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@mellanox.com>, dpdk stable <stable@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Gavin Hu <gavin.hu@arm.com>,
Pallantla Poornima <pallantlax.poornima@intel.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Reshma Pattan <reshma.pattan@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.9
Date: Tue, 27 Nov 2018 18:49:58 +0000 [thread overview]
Message-ID: <1543344598.5087.11.camel@debian.org> (raw)
In-Reply-To: <VI1PR05MB4269B5B090A1DD19AC23D7A2D7D00@VI1PR05MB4269.eurprd05.prod.outlook.com>
On Tue, 2018-11-27 at 12:55 +0000, Ali Alnubani wrote:
> Hi Luca,
>
> The following patches are not applicable in the stable branches
> (Please ignore them):
>
> net/mlx5: fix initialization of struct members http://patches.dpdk.or
> g/patch/48051/
> net/mlx4: fix initialization of struct members http://patches.dpdk.or
> g/patch/48050/
> net/mlx5: fix typos http://patches.dpdk.org/patch/48057/
> net/mlx4: fix typo http://patches.dpdk.org/patch/48056/
>
> I apologize for the mistake.
>
> Thanks,
> Ali
No worries, thanks for checking.
> > -----Original Message-----
> > From: Luca Boccassi <bluca@debian.org>
> > Sent: Monday, November 26, 2018 2:21 PM
> > To: dpdk stable <stable@dpdk.org>
> > Cc: Ali Alnubani <alialnu@mellanox.com>; Ferruh Yigit
> > <ferruh.yigit@intel.com>; Gavin Hu <gavin.hu@arm.com>; Pallantla
> > Poornima <pallantlax.poornima@intel.com>; Rasesh Mody
> > <rasesh.mody@cavium.com>; Reshma Pattan <reshma.pattan@intel.com>;
> > Shahaf Shuler <shahafs@mellanox.com>; Stephen Hemminger
> > <stephen@networkplumber.org>
> > 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:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fd
> > pd
> > k.org%2Fbrowse%2Fdpdk-
> > stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c2
> > 2997f20d19718e&data=02%7C01%7Calialnu%40mellanox.com%7Cbcb51
> > 6933b654626b23308d65399ae64%7Ca652971c7d2e4d9ba6a4d149256f461b%7
> > C0%7C0%7C636788316868045140&sdata=y3qFnX%2BVeoCE%2FbjkQNjF
> > s4DuBo89w0jhC4%2F%2FS126LHQ%3D&reserved=0
> >
> > 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
> >
> > ---
> > 0c15f3c01 Ali Alnubani net/mlx5: fix initialization of struct
> > members
> > 5835b7d37 Pallantla Poornima test/kni: fix module miss fallback
> > 853c78249 Rasesh Mody net/bnx2x: fix dynamic logging
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-11-27 18:50 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)
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 [this message]
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=1543344598.5087.11.camel@debian.org \
--to=bluca@debian.org \
--cc=alialnu@mellanox.com \
--cc=ferruh.yigit@intel.com \
--cc=gavin.hu@arm.com \
--cc=pallantlax.poornima@intel.com \
--cc=rasesh.mody@cavium.com \
--cc=reshma.pattan@intel.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).