From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Shahaf Shuler" <shahafs@mellanox.com>,
"Yongseok Koh" <yskoh@mellanox.com>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx: fix printing format specifiers
Date: Thu, 10 May 2018 20:39:12 +0100 [thread overview]
Message-ID: <137bdbb8-1e66-d131-e369-0ecb62e7cbcc@intel.com> (raw)
In-Reply-To: <DB7PR05MB4426991F6062BC9725304D8FC3980@DB7PR05MB4426.eurprd05.prod.outlook.com>
On 5/10/2018 11:58 AM, Shahaf Shuler wrote:
> Thursday, May 10, 2018 8:53 AM, Yongseok Koh:
>> Subject: [PATCH] net/mlx: fix printing format specifiers
>>
>> This will have to be squashed to:
>> net/mlx4: add new Memory Region support
>> net/mlx5: add new Memory Region support
>>
>> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
>> ---
>>
>> This is not a formal patch to merge but Shahaf will squash it separately to
>> mlx4 and mlx5 for dpdk-next-net.
>>
>> drivers/net/mlx4/mlx4_mr.c | 20 ++++++++++++--------
>> drivers/net/mlx5/mlx5_mr.c | 21 +++++++++++++--------
>> 2 files changed, 25 insertions(+), 16 deletions(-)
>>
>
> Squashed into the relevant commits on next-net-mlx, thanks.
>
> Ferruh -
> As Koh said, there are still 32b compilation errors on mlx5 origin before the memory series.
> Those should be fixed on a different commit.
Already replied in other thread but to be sure this is not missed, mlx5 already
doesn't claim 32bit support, so no need fixes for it.
prev parent reply other threads:[~2018-05-10 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 5:53 Yongseok Koh
2018-05-10 10:58 ` Shahaf Shuler
2018-05-10 19:39 ` Ferruh Yigit [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=137bdbb8-1e66-d131-e369-0ecb62e7cbcc@intel.com \
--to=ferruh.yigit@intel.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).