From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: acme@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6.26 1/2][SOCK]: Add udp_hash member to struct proto.
Date: Sat, 22 Mar 2008 16:55:59 -0700 (PDT) [thread overview]
Message-ID: <20080322.165559.236374100.davem@davemloft.net> (raw)
In-Reply-To: <47DFAC44.9020704@openvz.org>
From: Pavel Emelyanov <xemul@openvz.org>
Date: Tue, 18 Mar 2008 14:49:24 +0300
> Inspired by the commit ab1e0a13 ([SOCK] proto: Add hashinfo member to
> struct proto) from Arnaldo, I made similar thing for UDP/-Lite IPv4
> and -v6 protocols.
>
> The result is not that exciting, but it removes some levels of
> indirection in udpxxx_get_port and saves some space in code and text.
>
> The first step is to union existing hashinfo and new udp_hash on the
> struct proto and give a name to this union, since future initialization
> of tcpxxx_prot, dccp_vx_protinfo and udpxxx_protinfo will cause gcc
> warning about inability to initialize anonymous member this way.
>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Applied.
prev parent reply other threads:[~2008-03-22 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 11:49 [PATCH net-2.6.26 1/2][SOCK]: Add udp_hash member to struct proto Pavel Emelyanov
2008-03-22 23:55 ` 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=20080322.165559.236374100.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).