From: Sridhar Samudrala <sri@us.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net
Subject: Re: [PATCH 1/5][SCTP]: Implement SCTP_FRAGMENT_INTERLEAVE socket option.
Date: Wed, 21 Feb 2007 00:20:44 -0800 [thread overview]
Message-ID: <45DC00DC.8030504@us.ibm.com> (raw)
In-Reply-To: <20070220.232136.112621337.davem@davemloft.net>
David Miller wrote:
> From: Sridhar Samudrala <sri@us.ibm.com>
> Date: Fri, 16 Feb 2007 19:39:43 -0800
>
>
>> [SCTP]: Implement SCTP_FRAGMENT_INTERLEAVE socket option.
>>
>
> Sorry, these patches missed the merge window.
>
> Patches 4 and 5 are bug fixes, so I could apply just those if you
> want me to, just let me know and you don't need to resend them.
>
Yes. please apply patches 4 & 5 for 2.6.21. I will resubmit the
remaining when
2.6.22 merge window opens.
Thanks
Sridhar
next prev parent reply other threads:[~2007-02-21 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 3:39 [PATCH 1/5][SCTP]: Implement SCTP_FRAGMENT_INTERLEAVE socket option Sridhar Samudrala
2007-02-21 7:21 ` David Miller
2007-02-21 8:20 ` Sridhar Samudrala [this message]
2007-02-21 10:06 ` 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=45DC00DC.8030504@us.ibm.com \
--to=sri@us.ibm.com \
--cc=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@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 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).