From: Jon Grimm <jgrimm2@us.ibm.com>
To: Bruce Allan <bwa@us.ibm.com>
Cc: davem@redhat.com, lksctp-developers@lists.sourceforge.net,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [Lksctp-developers] [PATCH] subset of RFC2553
Date: Wed, 12 Feb 2003 20:24:22 -0600 [thread overview]
Message-ID: <3E4B01D6.3050604@us.ibm.com> (raw)
In-Reply-To: 1045091741.8858.320.camel@w-bwa1.beaverton.ibm.com
Bruce Allan wrote:
> and moves the definition of struct sockaddr_storage from the
> SCTP code to a common IPv6 header file. These changes will assist in
> making certain networking kernel code portable across multiple address
> families.
Hi Bruce,
I don't have any issue with moving sockaddr_storage out of lksctp
headers (though I don't own the decision to move them into the core
headers).
Thanks,
Jon Grimm
next prev parent reply other threads:[~2003-02-13 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 23:15 [PATCH] subset of RFC2553 Bruce Allan
2003-02-13 2:24 ` Jon Grimm [this message]
2003-02-13 5:43 ` David S. 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=3E4B01D6.3050604@us.ibm.com \
--to=jgrimm2@us.ibm.com \
--cc=bwa@us.ibm.com \
--cc=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.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).