lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20190204.120727.1732794761205124286.davem@davemloft.net> Date: Mon, 04 Feb 2019 12:07:27 -0800 (PST) From: David Miller <davem@...emloft.net> To: yihung.wei@...il.com Cc: elibr@...lanox.com, pshelar@....org, dev@...nvswitch.org, netdev@...r.kernel.org, simon.horman@...ronome.com Subject: Re: [ovs-dev] [PATCH net-next V2 1/1] openvswitch: Declare ovs key structures using macros From: Yi-Hung Wei <yihung.wei@...il.com> Date: Mon, 4 Feb 2019 10:47:18 -0800 > For example, to see how 'struct ovs_key_ipv6' is defined, now we need > to trace how OVS_KEY_IPV6_FIELDS is defined, and how OVS_KEY_FIELD_ARR > and OVS_KEY_FIELD defined. I think it makes the header file to be > more complicated. I completely agree. Unless this is totally unavoidable, I do not want to apply a patch which makes reading and auditing the networking code more difficult.
Powered by blists - more mailing lists