From: Brian Haley <brian.haley@hp.com>
To: dccp@vger.kernel.org
Subject: [PATCH 0/4] [IPv6] Add new scope and address type inlines
Date: Fri, 06 Apr 2007 03:19:25 +0000 [thread overview]
Message-ID: <4615BC3D.8010803@hp.com> (raw)
[sorry if anyone got these multiple times, git-send-email weirdness]
This set of patches adds new IPv6 scope and address type inlines
to both clean-up the code (inspired by Arnaldo's skb cleanup) and reduce
calls to ipv6_addr_type() when we can just compare the address directly.
No functionality is changed.
I'm only cc'ing the DCCP and LkSCTP lists on the patches that actually
touch their code.
-Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, dccp@vger.kernel.org,
lksctp-developers@lists.sourceforge.net
Subject: [PATCH 0/4] [IPv6] Add new scope and address type inlines
Date: Thu, 05 Apr 2007 23:19:25 -0400 [thread overview]
Message-ID: <4615BC3D.8010803@hp.com> (raw)
[sorry if anyone got these multiple times, git-send-email weirdness]
This set of patches adds new IPv6 scope and address type inlines
to both clean-up the code (inspired by Arnaldo's skb cleanup) and reduce
calls to ipv6_addr_type() when we can just compare the address directly.
No functionality is changed.
I'm only cc'ing the DCCP and LkSCTP lists on the patches that actually
touch their code.
-Brian
next reply other threads:[~2007-04-06 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 3:19 Brian Haley [this message]
2007-04-06 3:19 ` [PATCH 0/4] [IPv6] Add new scope and address type inlines Brian Haley
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=4615BC3D.8010803@hp.com \
--to=brian.haley@hp.com \
--cc=dccp@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.