All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
	Dekel Peled <dekelp@mellanox.com>,
	Ali Alnubani <alialnu@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] net/mlx5: add missing return value check
Date: Wed, 27 Mar 2019 09:31:29 +0000	[thread overview]
Message-ID: <7e6eeec8-8c0c-4935-2bc9-9b07755e08ea@intel.com> (raw)
In-Reply-To: <9fa4371f-cf9d-79f8-9868-e45bd882e9c5@intel.com>

On 3/25/2019 12:02 PM, Ferruh Yigit wrote:
> On 3/24/2019 9:26 AM, Shahaf Shuler wrote:
>> Thursday, March 21, 2019 11:34 AM, Dekel Peled:
>>> Subject: RE: [PATCH] net/mlx5: add missing return value check
>>>
>>>> -----Original Message-----
>>>> From: Ali Alnubani
>>>> Sent: Thursday, March 21, 2019 11:07 AM
>>>> To: dev@dpdk.org
>>>> Cc: Shahaf Shuler <shahafs@mellanox.com>; Dekel Peled
>>>> <dekelp@mellanox.com>
>>>> Subject: [PATCH] net/mlx5: add missing return value check
>>>>
>>>> Fixes: d86406b965df ("net/mlx5: support new representor naming
>>>> format")
>>>> Cc: dekelp@mellanox.com
>>>>
>>>> Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
>>
>> Applied to next-net-mlx, thanks. 
>>
> 
> Squashed into relevant commit [1] in next-net, thanks.
> 
> [1]
> net/mlx5: support new representor naming format
> 

'main' repo get the original patch without squash, so can't squash now,
merged as a incremental patch ...

Applied to dpdk-next-net/master, thanks.

  reply	other threads:[~2019-03-27  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  9:07 [PATCH] net/mlx5: add missing return value check Ali Alnubani
2019-03-21  9:26 ` Slava Ovsiienko
2019-03-21  9:34 ` Dekel Peled
2019-03-24  9:26   ` Shahaf Shuler
2019-03-25 12:02     ` Ferruh Yigit
2019-03-27  9:31       ` Ferruh Yigit [this message]
2019-03-28 10:29         ` Ali Alnubani
2019-03-28 18:28           ` 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=7e6eeec8-8c0c-4935-2bc9-9b07755e08ea@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=alialnu@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.