DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andy Green <andy@warmcat.com>
To: Shahaf Shuler <shahafs@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yongseok Koh" <yskoh@mellanox.com>,
	"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
	"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 3/4] net/mlx5: solve var may be used uninitialized
Date: Sun, 13 May 2018 13:25:12 +0800	[thread overview]
Message-ID: <3d1b90be-dd25-4f4f-74b2-3337a51277b9@warmcat.com> (raw)
In-Reply-To: <DB7PR05MB44263CAA13563C250DAD47E0C39D0@DB7PR05MB4426.eurprd05.prod.outlook.com>



On 05/13/2018 12:45 PM, Shahaf Shuler wrote:
> Hi Andy
> 
> The patch logic is OK but:
> 1. since it is a fix patch the title should start with "fix ..."
> 2. add Fixes tag of the relevant commit and Cc stable if needed
> 3. add signed-of-by tag
> 4. explicitly include the PMD maintainers (Cc'ed now).

For a patch adding 4 characters, from a drive-by, it's a lot of overhead.

There's already a V2 of this sent yesterday with the signed-off-by (OK, 
that is not really any overhead) and most of the rest of your stuff 
donated by Pablo.

-Andy

> Friday, May 11, 2018 4:51 AM, Andy Green
>> Subject: [dpdk-dev] [PATCH 3/4] net/mlx5: solve var may be used
>> uninitialized
>>
>>
>> ---
>>   drivers/net/mlx5/mlx5.c |    2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c index
>> 8f983061a..4d379fb13 100644
>> --- a/drivers/net/mlx5/mlx5.c
>> +++ b/drivers/net/mlx5/mlx5.c
>> @@ -624,7 +624,7 @@ mlx5_pci_probe(struct rte_pci_driver *pci_drv
>> __rte_unused,
>>   	int err = 0;
>>   	struct ibv_context *attr_ctx = NULL;
>>   	struct ibv_device_attr_ex device_attr;
>> -	unsigned int vf;
>> +	unsigned int vf = 0;
>>   	unsigned int mps;
>>   	unsigned int cqe_comp;
>>   	unsigned int tunnel_en = 0;
> 

  reply	other threads:[~2018-05-13  5:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  1:51 [dpdk-dev] [PATCH 0/4] GCC8 fixes for MLX4/5/BNX2X PMD Andy Green
2018-05-11  1:51 ` [dpdk-dev] [PATCH 1/4] net/bnx2x: do not cast function pointers as a policy Andy Green
2018-05-11 16:03   ` Ferruh Yigit
2018-05-12  0:25     ` Andy Green
2018-05-11 16:33   ` De Lara Guarch, Pablo
2018-05-11  1:51 ` [dpdk-dev] [PATCH 2/4] net/bnx2x: remove unmeetable comparison Andy Green
2018-05-11 16:32   ` De Lara Guarch, Pablo
2018-05-11 18:10     ` Stephen Hemminger
2018-05-12  1:04       ` Andy Green
2018-05-11  1:51 ` [dpdk-dev] [PATCH 3/4] net/mlx5: solve var may be used uninitialized Andy Green
2018-05-11 16:25   ` De Lara Guarch, Pablo
2018-05-13  4:45   ` Shahaf Shuler
2018-05-13  5:25     ` Andy Green [this message]
2018-05-11  1:51 ` [dpdk-dev] [PATCH 4/4] net/bnx2x: solve overruns Andy Green
2018-05-11 16:21   ` De Lara Guarch, Pablo
2018-05-11 16:04 ` [dpdk-dev] [PATCH 0/4] GCC8 fixes for MLX4/5/BNX2X PMD Ferruh Yigit

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=3d1b90be-dd25-4f4f-74b2-3337a51277b9@warmcat.com \
    --to=andy@warmcat.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.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).