From: Or Gerlitz <ogerlitz@mellanox.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Scott Feldman <sfeldma@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: gone with the spring cleanup..
Date: Wed, 13 May 2015 13:55:57 +0300 [thread overview]
Message-ID: <55532DBD.1080901@mellanox.com> (raw)
In-Reply-To: <20150513104249.GB2136@nanopsycho.mtl.com>
On 5/13/2015 1:42 PM, Jiri Pirko wrote:
>> Looks like the problem might be in named structures which suppose to be
>> >anonymous. Would you try following patch:
> oh, switchdev_obj_vlan and switchdev_obj_ipv4_fib is used in rocker..
> So better:
nope, fails.. if I remove the union (it is struct switchdev_obj has
strict vlan and ipv4_fib fields) it works. Seems there's some problem
also with anonymous unions.
>
> diff --git a/include/net/switchdev.h b/include/net/switchdev.h
> index 3b217b4..32ce31d 100644
> --- a/include/net/switchdev.h
> +++ b/include/net/switchdev.h
> @@ -49,24 +49,28 @@ enum switchdev_obj_id {
> SWITCHDEV_OBJ_IPV4_FIB,
> };
>
> +struct switchdev_obj_vlan {
> + u16 flags;
> + u16 vid_start;
> + u16 vid_end;
> +};
> +
> +struct switchdev_obj_ipv4_fib {
> + u32 dst;
> + int dst_len;
> + struct fib_info *fi;
> + u8 tos;
> + u8 type;
> + u32 nlflags;
> + u32 tb_id;
> +};
> +
> struct switchdev_obj {
> enum switchdev_obj_id id;
> enum switchdev_trans trans;
> union {
> - struct switchdev_obj_vlan { /* PORT_VLAN */
> - u16 flags;
> - u16 vid_start;
> - u16 vid_end;
> - } vlan;
> - struct switchdev_obj_ipv4_fib { /* IPV4_FIB */
> - u32 dst;
> - int dst_len;
> - struct fib_info *fi;
> - u8 tos;
> - u8 type;
> - u32 nlflags;
> - u32 tb_id;
> - } ipv4_fib;
> + struct switchdev_obj_vlan vlan;
> + struct switchdev_obj_ipv4_fib ipv4_fib;
> };
> };
>
next prev parent reply other threads:[~2015-05-13 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 9:12 gone with the spring cleanup Or Gerlitz
2015-05-13 10:38 ` Jiri Pirko
2015-05-13 10:42 ` Jiri Pirko
2015-05-13 10:55 ` Or Gerlitz [this message]
2015-05-13 11:26 ` Daniel Borkmann
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=55532DBD.1080901@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sfeldma@gmail.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).