From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Benc <jbenc@redhat.com>
Cc: netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
James Chapman <jchapman@katalix.com>,
Paul Moore <paul@paul-moore.com>,
Pravin Shelar <pshelar@nicira.com>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH net-next 0/4] netlink: access functions for IP address attributes
Date: Sun, 29 Mar 2015 21:02:33 +0200 [thread overview]
Message-ID: <1427655753.2101.0.camel@sipsolutions.net> (raw)
In-Reply-To: <cover.1427639592.git.jbenc@redhat.com>
On Sun, 2015-03-29 at 16:59 +0200, Jiri Benc wrote:
> 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.
Looks fine to me as far as the conversion is concerned, it's not code we
touch much so feel free to take through any tree you like.
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
next prev parent reply other threads:[~2015-03-29 19:02 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 ` Johannes Berg [this message]
2015-03-31 17:58 ` [PATCH net-next 0/4] netlink: access functions for IP address attributes 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=1427655753.2101.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=herbert@gondor.apana.org.au \
--cc=jbenc@redhat.com \
--cc=jchapman@katalix.com \
--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).