From: Yongseok Koh <yskoh@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
"somnath.kotur@broadcom.com" <somnath.kotur@broadcom.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 17.11.7
Date: Fri, 2 Aug 2019 00:37:41 +0000 [thread overview]
Message-ID: <E62BC056-D143-4E30-9393-A54555019BEF@mellanox.com> (raw)
In-Reply-To: <20190726111426.41b5169d@hermes.lan>
> On Jul 26, 2019, at 11:14 AM, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Mon, 22 Jul 2019 18:40:23 -0700
> Yongseok Koh <yskoh@mellanox.com> wrote:
>
>> Hi commit authors (and maintainers),
>>
>> I didn't manage to apply following commits from upstream to stable branch 17.11:
>
>> f06515964a Stephen Hemminger net/bnxt: silence IOVA warnings
>> 618bbdab47 Stephen Hemminger net/bnxt: suppress spurious error log
>
> These should be reviewed by bnxt maintainers
Copying bnxt maintainers.
>> 869bf6d222 Stephen Hemminger net/ring: fix coding style
>
> This is a style only patch not needed for stable.
Removed from the list.
>> 8f37e38241 Stephen Hemminger net/virtio: fix buffer leak on VLAN insert
>
> This should just be merged, easy to do.
I just trimmed the original patch and merged.
Thanks,
Yongseok
next prev parent reply other threads:[~2019-08-02 0:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190723014023.30544-1-yskoh@mellanox.com>
2019-07-25 7:03 ` [dpdk-stable] 答复: " Joyce Kong (Arm Technology China)
2019-08-02 0:08 ` [dpdk-stable] " Yongseok Koh
2019-07-26 18:14 ` Stephen Hemminger
2019-08-02 0:37 ` Yongseok Koh [this message]
2019-08-02 8:02 ` Somnath Kotur
2019-08-02 21:33 ` Yongseok Koh
2019-08-09 5:28 ` Hyong Youb Kim (hyonkim)
2019-08-12 18:44 ` Yongseok Koh
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=E62BC056-D143-4E30-9393-A54555019BEF@mellanox.com \
--to=yskoh@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=somnath.kotur@broadcom.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).