From: Hyong Youb Kim <hyonkim@cisco.com>
To: luca.boccassi@gmail.com
Cc: dpdk stable <stable@dpdk.org>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Didier Pallard <didier.pallard@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Jasvinder Singh <jasvinder.singh@intel.com>,
Jianfeng Tan <jianfeng.tan@intel.com>,
John Daley <johndale@cisco.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Yongseok Koh <yskoh@mellanox.com>,
Yong Wang <yongwang@vmware.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 18.02.2
Date: Wed, 2 May 2018 15:04:18 +0900 [thread overview]
Message-ID: <20180502060417.GA16112@HYONKIM-FTCPE.cisco.com> (raw)
In-Reply-To: <20180430152307.4249-1-luca.boccassi@gmail.com>
On Mon, Apr 30, 2018 at 04:23:07PM +0100, luca.boccassi@gmail.com wrote:
> Hi commit authors (and maintainers),
>
> I didn't manage to apply following commits from upstream to stable branch
> 18.02: conflict happens. I'm wondering can the authors check the following
> list and backport those patches belong to you?
[...]
> 05e856826 John Daley net/enic: fix uninitialized variable
You can drop this patch, as it depends on another patch that is not in
18.02.
Thanks.
-Hyong
next prev parent reply other threads:[~2018-05-02 6:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:23 luca.boccassi
2018-04-30 15:30 ` Maxime Coquelin
2018-04-30 15:44 ` Luca Boccassi
2018-04-30 16:06 ` Burakov, Anatoly
2018-04-30 16:33 ` Luca Boccassi
2018-05-02 6:04 ` Hyong Youb Kim [this message]
2018-05-02 10:43 ` Luca Boccassi
2018-05-02 8:27 ` Nélio Laranjeiro
2018-05-02 10:42 ` Luca Boccassi
2018-05-18 9:46 ` luca.boccassi
2018-05-18 10:11 ` Richardson, Bruce
2018-05-18 10:21 ` Luca Boccassi
2018-05-18 10:25 ` Andy Green
2018-05-18 10:33 ` Pattan, Reshma
2018-05-18 10:36 ` Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 1/5] eal: support strlcpy function Andy Green
2018-05-18 11:37 ` [dpdk-stable] [PATCH 2/5] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 3/5] net/qede: fix strncpy Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 4/5] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 11:38 ` [dpdk-stable] [PATCH 5/5] net/sfc: make sure that stats name is nul-terminated Andy Green
2018-05-18 13:13 ` [dpdk-stable] [PATCH 0/5] 18.02 Requested backports Luca Boccassi
2018-05-25 17:23 ` [dpdk-stable] please help backporting some patches to stable release 18.02.2 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=20180502060417.GA16112@HYONKIM-FTCPE.cisco.com \
--to=hyonkim@cisco.com \
--cc=adrien.mazarguil@6wind.com \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=cristian.dumitrescu@intel.com \
--cc=didier.pallard@6wind.com \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jasvinder.singh@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=johndale@cisco.com \
--cc=luca.boccassi@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yongwang@vmware.com \
--cc=yskoh@mellanox.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).