From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] IPv6 updates
Date: Sun, 13 Jan 2013 20:32:55 -0500 (EST) [thread overview]
Message-ID: <20130113.203255.1305411796615468589.davem@davemloft.net> (raw)
In-Reply-To: <50F2CCA0.4080500@linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Mon, 14 Jan 2013 00:02:56 +0900
> Hello.
>
> YOSHIFUJI Hideaki (7):
> ipv6: Introduce ip6_flow_hdr() to fill version, tclass and flowlabel.
> ipv6: Introduce ip6_flowinfo() to extract flowinfo (tclass +
> flowlabel).
> ipv6: Use ipv6_get_dsfield() instead of ipv6_tclass().
> ipv6: Make ipv6_is_mld() inline and use it from ip6_mc_input().
> ipv6 route: Use ipv6_addr_hash() in rt6_info_hash_nhsfn().
> ipv6 xfrm: Use ipv6_addr_hash() in xfrm6_tunnel_spi_hash_byaddr().
> ipv6: Store Router Alert option in IP6CB directly.
Series applied, thanks.
prev parent reply other threads:[~2013-01-14 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 15:02 [PATCH net-next 0/7] IPv6 updates YOSHIFUJI Hideaki
2013-01-14 1:32 ` 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=20130113.203255.1305411796615468589.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).