All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
	Mordechay Haimovsky <motih@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v5 4/4] net/mlx5: support e-switch flow count action
Date: Tue, 23 Oct 2018 09:40:09 +0100	[thread overview]
Message-ID: <8199e0b4-2f75-af77-b088-fae19b3ece87@intel.com> (raw)
In-Reply-To: <DB7PR05MB442628EEDAEAA1C2C39A620CC3F40@DB7PR05MB4426.eurprd05.prod.outlook.com>

On 10/22/2018 9:10 PM, Shahaf Shuler wrote:
> Ferruh,
> 
> Monday, October 22, 2018 12:15 PM, Ferruh Yigit:
>> Subject: Re: [dpdk-dev] [PATCH v5 4/4] net/mlx5: support e-switch flow
>> count action
>>
>> Getting following build error with clang, will not pull from mlx tree until issue
>> resolved, thanks.
>>
>> .../drivers/net/mlx5/mlx5_flow_tcf.c:2507:6: warning: cast from 'const struct
>> rtattr *' to 'char *' drops const qualifier [-Wcast-qual]
>>                                  RTA_DATA(arg), RTA_PAYLOAD(arg));
>>                                  ^
>> /usr/include/linux/rtnetlink.h:183:42: note: expanded from macro
>> 'RTA_DATA'
>> #define RTA_DATA(rta)   ((void*)(((char*)(rta)) + RTA_LENGTH(0)))
>>                                          ^
>> .../drivers/net/mlx5/mlx5_flow_tcf.c:2593:31: warning: cast from 'const
>> struct nlmsghdr *' to 'char *' drops const qualifier [-Wcast-qual]
>>         struct tcmsg *t = NLMSG_DATA(nlh);
> 
> I updated next-net-mlx with the fix for this issue. Can you confirm it is fixed? 

I confirm it is good, pulled from next-net-mlx.

      reply	other threads:[~2018-10-23  8:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 13:04 [PATCH v2 0/2] support e-switch flow count action Mordechay Haimovsky
2018-10-11 13:04 ` [PATCH v2 1/2] net/mlx5: refactor TC-flow infrastructure Mordechay Haimovsky
2018-10-14 11:07   ` Shahaf Shuler
2018-10-11 13:04 ` [PATCH v2 2/2] net/mlx5: support e-switch flow count action Mordechay Haimovsky
2018-10-14 11:07   ` Shahaf Shuler
2018-10-16 23:50   ` [PATCH v3 0/2] " Mordechay Haimovsky
2018-10-16 23:50   ` [PATCH v3 1/2] net/mlx5: refactor TC-flow infrastructure Mordechay Haimovsky
2018-10-16 23:50   ` [PATCH v3 2/2] net/mlx5: support e-switch flow count action Mordechay Haimovsky
2018-10-17 17:24     ` [PATCH v4 0/3] " Moti Haimovsky
2018-10-17 17:24     ` [PATCH v4 1/3] net/mlx5: refactor TC-flow infrastructure Moti Haimovsky
2018-10-17 17:24     ` [PATCH v4 2/3] net/mlx5: add flow query abstraction interface Moti Haimovsky
2018-10-17 17:24     ` [PATCH v4 3/3] net/mlx5: support e-switch flow count action Moti Haimovsky
2018-10-18 18:29       ` [PATCH v5 0/4] " Moti Haimovsky
2018-10-21  8:23         ` Shahaf Shuler
2018-10-18 18:29       ` [PATCH v5 1/4] net/mlx5: refactor TC-flow infrastructure Moti Haimovsky
2018-10-18 18:29       ` [PATCH v5 2/4] net/mlx5: tc flow to use the new infrastructure Moti Haimovsky
2018-10-18 18:29       ` [PATCH v5 3/4] net/mlx5: add flow query abstraction interface Moti Haimovsky
2018-10-18 18:29       ` [PATCH v5 4/4] net/mlx5: support e-switch flow count action Moti Haimovsky
2018-10-22  9:14         ` Ferruh Yigit
2018-10-22 20:10           ` Shahaf Shuler
2018-10-23  8:40             ` 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=8199e0b4-2f75-af77-b088-fae19b3ece87@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=motih@mellanox.com \
    --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.