From: David Miller <davem@davemloft.net>
To: jbenc@redhat.com
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, jchapman@katalix.com,
paul@paul-moore.com, pshelar@nicira.com,
johannes@sipsolutions.net, pablo@netfilter.org
Subject: Re: [PATCH net-next 0/4] netlink: access functions for IP address attributes
Date: Tue, 31 Mar 2015 13:58:56 -0400 (EDT) [thread overview]
Message-ID: <20150331.135856.1727900367681294283.davem@davemloft.net> (raw)
In-Reply-To: <cover.1427639592.git.jbenc@redhat.com>
From: Jiri Benc <jbenc@redhat.com>
Date: Sun, 29 Mar 2015 16:59:22 +0200
> There are many places that read or write IP addresses to netlink attributes.
> With IPv6 addresses, every such place currently has to use generic nla_put
> and nla_memcpy. Implementing IPv6 address access functions simplify things
> and makes the code more intelligible. IPv4 address access functions has
> lesser value but it would be better to be consistent between IPv6 and IPv4
> and they still serve as documentation.
>
> The conversion is straightforward and the resulting patches are not that
> large, thus I kept all the changes in the patches that introduce the access
> functions. If anyone prefers to split the definition of access functions and
> the conversion and/or break it out by network protocols, please let me know.
>
> While doing the conversion, I came across ugly typecasting in
> inetpeer_addr_base and xfrm_address_t when dealing with IPv6 addresses.
> Instead of introducing more of this, I cleaned it up. Those are the first
> two patches, serving as a prerequisite to the latter two.
Looks good, series applied, thanks Jiri.
prev parent reply other threads:[~2015-03-31 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 14:59 [PATCH net-next 0/4] netlink: access functions for IP address attributes Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 1/4] tcp: simplify inetpeer_addr_base use Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 2/4] xfrm: simplify xfrm_address_t use Jiri Benc
2015-04-07 16:01 ` Stephen Hemminger
2015-04-07 16:29 ` Jiri Benc
2015-04-07 16:35 ` Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 3/4] netlink: implement nla_put_in_addr and nla_put_in6_addr Jiri Benc
2015-03-29 14:59 ` [PATCH net-next 4/4] netlink: implement nla_get_in_addr and nla_get_in6_addr Jiri Benc
2015-03-29 19:02 ` [PATCH net-next 0/4] netlink: access functions for IP address attributes Johannes Berg
2015-03-31 17:58 ` David Miller [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=20150331.135856.1727900367681294283.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jbenc@redhat.com \
--cc=jchapman@katalix.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=paul@paul-moore.com \
--cc=pshelar@nicira.com \
--cc=steffen.klassert@secunet.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).