From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: lksctp-developers@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] [SCTP] Do not interleave non-fragments when in partial delivery
Date: Wed, 18 Apr 2007 13:24:08 -0700 (PDT) [thread overview]
Message-ID: <20070418.132408.15264893.davem@davemloft.net> (raw)
In-Reply-To: <46266597.2000705@hp.com>
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Wed, 18 Apr 2007 14:38:15 -0400
> This is a bug fix, but done on top of 2.6.22 tree. I am trying
> to minimize the amount of conflict this would cause during merge
> by doing it this way. However, if you would rather keep all the bugfixes
> in net-2.6, I can do that too, but that _will_ give you conflicts.
I've already determined that I'm destined to deal with tons
of conclicts anyways :-)
I'll backport this to net-2.6 unless you beat me to it :-)
Thanks!
next prev parent reply other threads:[~2007-04-18 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 18:38 [PATCH] [SCTP] Do not interleave non-fragments when in partial delivery Vlad Yasevich
2007-04-18 20:24 ` David Miller [this message]
2007-04-18 20:52 ` Vlad Yasevich
2007-04-18 21:11 ` 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=20070418.132408.15264893.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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).