From: Luca Boccassi <luca.boccassi@gmail.com>
To: Andy Green <andy@warmcat.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 0/4] 16.11 Requested backports
Date: Fri, 18 May 2018 13:48:29 +0100 [thread overview]
Message-ID: <1526647709.23337.139.camel@gmail.com> (raw)
In-Reply-To: <152664553026.32615.51601026908782839.stgit@localhost.localdomain>
On Fri, 2018-05-18 at 20:15 +0800, Andy Green wrote:
> The following series are the requested patches including
> the BR patch introducing strlcpy and excluding a patch
> that in not needed, same as on 18.02.
>
> I am unable to build test it, since even on trusty 16.11 build spews
> errors even without any changes.
>
> However it probably builds since it's based on 18.02 with
> the removal of some stuff caught in the diff for those patches
> that doesn't exist on 16.11.
Thanks, applied and pushed. I verified it builds on Debian 9 both with
and without _LIBBSD.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-05-18 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 10:49 [dpdk-stable] please help backporting some patches to LTS release 16.11.7 luca.boccassi
2018-05-07 2:08 ` Chen, Junjie J
2018-05-08 9:50 ` Luca Boccassi
2018-05-18 9:47 ` luca.boccassi
2018-05-18 12:15 ` [dpdk-stable] [PATCH 0/4] 16.11 Requested backports Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 1/4] eal: support strlcpy function Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 2/4] bus/pci: fix size of driver name buffer Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 3/4] net/qede: fix strncpy Andy Green
2018-05-18 12:16 ` [dpdk-stable] [PATCH 4/4] net/qede: replace strncpy by strlcpy Andy Green
2018-05-18 12:48 ` Luca Boccassi [this message]
2018-05-25 17:24 ` [dpdk-stable] please help backporting some patches to LTS release 16.11.7 luca.boccassi
2018-05-29 21:59 ` Shaikh, Shahed
2018-05-29 22:55 ` 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=1526647709.23337.139.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=andy@warmcat.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).