From: Thomas Monjalon <thomas@monjalon.net>
To: Andy Green <andy@warmcat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/4] GCC8 fixes for MLX4/5/BNX2X PMD
Date: Tue, 15 May 2018 22:30:50 +0200 [thread overview]
Message-ID: <2054231.zYh5meLfVJ@xps> (raw)
In-Reply-To: <152627420173.53058.13179290989817984940.stgit@localhost.localdomain>
> Andy Green (4):
> net/bnx2x: do not cast function pointers as a policy
> net/bnx2x: correct unmeetable comparison
> net/mlx5: solve var may be used uninitialized
> net/bnx2x: solve overruns
Series applied, thanks
prev parent reply other threads:[~2018-05-15 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 1:51 [dpdk-dev] [PATCH v2 " Andy Green
2018-05-12 1:51 ` [dpdk-dev] [PATCH v2 1/4] net/bnx2x: do not cast function pointers as a policy Andy Green
2018-05-12 1:51 ` [dpdk-dev] [PATCH v2 2/4] net/bnx2x: correct unmeetable comparison Andy Green
2018-05-12 1:51 ` [dpdk-dev] [PATCH v2 3/4] net/mlx5: solve var may be used uninitialized Andy Green
2018-05-12 1:51 ` [dpdk-dev] [PATCH v2 4/4] net/bnx2x: solve overruns Andy Green
2018-05-14 5:04 ` [dpdk-dev] [PATCH v3 0/4] GCC8 fixes for MLX4/5/BNX2X PMD Andy Green
2018-05-14 5:04 ` [dpdk-dev] [PATCH v3 1/4] net/bnx2x: do not cast function pointers as a policy Andy Green
2018-05-15 19:47 ` Mody, Rasesh
2018-05-14 5:04 ` [dpdk-dev] [PATCH v3 2/4] net/bnx2x: correct unmeetable comparison Andy Green
2018-05-14 11:17 ` Ferruh Yigit
2018-05-14 22:17 ` Mody, Rasesh
2018-05-14 22:16 ` Mody, Rasesh
2018-05-15 14:46 ` Thomas Monjalon
2018-05-15 19:52 ` Mody, Rasesh
2018-05-14 5:04 ` [dpdk-dev] [PATCH v3 3/4] net/mlx5: solve var may be used uninitialized Andy Green
2018-05-15 17:25 ` Yongseok Koh
2018-05-14 5:04 ` [dpdk-dev] [PATCH v3 4/4] net/bnx2x: solve overruns Andy Green
2018-05-15 19:47 ` Mody, Rasesh
2018-05-15 20:30 ` Thomas Monjalon [this message]
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=2054231.zYh5meLfVJ@xps \
--to=thomas@monjalon.net \
--cc=andy@warmcat.com \
--cc=dev@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).