From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jhs@mojatatu.com,
stephen@networkplumber.org, pshelar@nicira.com,
aar@pengutronix.de, linux-wpan@vger.kernel.org,
wensong@linux-vs.org, horms@verge.net.au, ja@ssi.bg,
pablo@netfilter.org, kaber@trash.net, kadlec@blackhole.kfki.hu,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: [PATCH net-next 0/9] netlink: align attributes when needed (patchset #2)
Date: Mon, 25 Apr 2016 10:25:13 +0200 [thread overview]
Message-ID: <1461572722-6029-1-git-send-email-nicolas.dichtel@6wind.com> (raw)
This is the continuation (series #2) of the work done to align netlink
attributes when these attributes contain some 64-bit fields.
In patch #3, I didn't modify the function ila_encap_nlsize(). I was waiting
feedback for this patch: http://patchwork.ozlabs.org/patch/613766/
If it's approved, there will be an update to switch nla_total_size() to
nla_total_size_64bit() after the merge of net in net-next.
include/linux/nl802154.h | 2 +
include/uapi/linux/if_link.h | 3 ++
include/uapi/linux/ila.h | 1 +
include/uapi/linux/ip_vs.h | 1 +
include/uapi/linux/l2tp.h | 1 +
include/uapi/linux/nl80211.h | 4 ++
include/uapi/linux/openvswitch.h | 1 +
include/uapi/linux/pkt_sched.h | 3 ++
net/bridge/br_netlink.c | 62 +++++++++++++++------------
net/core/rtnetlink.c | 36 ++++++++--------
net/ieee802154/nl-mac.c | 17 +++++---
net/ieee802154/nl802154.c | 3 +-
net/ipv6/ila/ila_lwt.c | 3 +-
net/ipv6/ila/ila_xlat.c | 15 ++++---
net/l2tp/l2tp_netlink.c | 80 +++++++++++++++++++++--------------
net/netfilter/ipvs/ip_vs_ctl.c | 36 ++++++++++------
net/openvswitch/datapath.c | 3 +-
net/sched/sch_htb.c | 6 ++-
net/sched/sch_netem.c | 3 +-
net/sched/sch_tbf.c | 6 ++-
net/wireless/nl80211.c | 91 ++++++++++++++++++++++++----------------
21 files changed, 233 insertions(+), 144 deletions(-)
Comments are welcomed,
Regards,
Nicolas
next reply other threads:[~2016-04-25 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 8:25 Nicolas Dichtel [this message]
2016-04-25 8:25 ` [PATCH net-next 1/9] rtnl: use nla_put_u64_64bit() Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 2/9] sched: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 3/9] ipv6: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 4/9] ovs: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 5/9] bridge: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 6/9] l2tp: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 7/9] ieee802154: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 8/9] netfilter/ipvs: " Nicolas Dichtel
2016-04-25 8:25 ` [PATCH net-next 9/9] wireless: " Nicolas Dichtel
2016-04-26 7:39 ` Johannes Berg
2016-04-26 7:51 ` Nicolas Dichtel
2016-04-25 19:09 ` [PATCH net-next 0/9] netlink: align attributes when needed (patchset #2) David Miller
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=1461572722-6029-1-git-send-email-nicolas.dichtel@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=aar@pengutronix.de \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=jhs@mojatatu.com \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pshelar@nicira.com \
--cc=stephen@networkplumber.org \
--cc=wensong@linux-vs.org \
/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).