From: Jiri Pirko <jiri@resnulli.us>
To: David Laight <David.Laight@ACULAB.COM>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, thaller@redhat.com, stephen@networkplumber.org,
hannes@stressinduktion.org, vyasevich@gmail.com, dcbw@redhat.com
Subject: Re: [patch net-next RFC 1/2] ipv6 addrconf: extend ifa_flags to u32
Date: Mon, 11 Nov 2013 16:12:07 +0100 [thread overview]
Message-ID: <20131111151207.GA2463@minipsycho.orion> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B73FA@saturn3.aculab.com>
Mon, Nov 11, 2013 at 04:07:20PM CET, David.Laight@ACULAB.COM wrote:
>> --- a/include/net/if_inet6.h
>> +++ b/include/net/if_inet6.h
>> @@ -51,7 +51,7 @@ struct inet6_ifaddr {
>> int state;
>>
>> __u8 dad_probes;
>> - __u8 flags;
>> + __u32 flags;
>>
>> __u16 scope;
>
>That is adding a lot of padding.
Allright. Will reorder. Thanks
>
> David
>
>
>
next prev parent reply other threads:[~2013-11-11 15:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:49 [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses Jiri Pirko
2013-11-11 14:49 ` [patch net-next RFC 1/2] ipv6 addrconf: extend ifa_flags to u32 Jiri Pirko
2013-11-11 15:07 ` David Laight
2013-11-11 15:12 ` Jiri Pirko [this message]
2013-11-11 14:49 ` [patch net-next RFC 2/2] ipv6 addrconf: introduce IFA_F_MANAGETEMPADDR to tell kernel to manage temporary addresses Jiri Pirko
2013-11-15 17:48 ` [PATCH 1/1] fixup! " Thomas Haller
2013-11-18 10:23 ` Jiri Pirko
2013-11-15 18:04 ` [patch net-next RFC 2/2] " Thomas Haller
2013-11-11 14:50 ` [patch iproute2 RFC 1/2] add support for extended ifa_flags Jiri Pirko
2013-11-11 14:50 ` [patch iproute2 RFC 2/2] add support for IFA_F_MANAGETEMPADDR Jiri Pirko
2013-11-11 18:42 ` [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses David Miller
2013-11-11 19:49 ` Jiri Pirko
2013-11-11 20:01 ` David Miller
2013-11-11 21:04 ` Jiri Pirko
2013-11-11 23:03 ` 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=20131111151207.GA2463@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=thaller@redhat.com \
--cc=vyasevich@gmail.com \
--cc=yoshfuji@linux-ipv6.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).