From: "David S. Miller" <davem@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev@oss.sgi.com, lksctp-developers@lists.sourceforge.net
Subject: Re: [BK PATCH] 2.4 SCTP updates
Date: Tue, 6 Apr 2004 13:52:31 -0700 [thread overview]
Message-ID: <20040406135231.63608955.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404061157100.8396@localhost.localdomain>
Both 2.4.x and 2.6.x trees pulled, thanks Sridhar.
Don't worry about the pagealloc debugging issue in 2.4.x
next prev parent reply other threads:[~2004-04-06 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 19:09 [BK PATCH] 2.4 SCTP updates Sridhar Samudrala
2004-04-06 20:52 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-13 0:24 Sridhar Samudrala
2004-08-13 1:00 ` David S. Miller
2004-03-23 20:15 Sridhar Samudrala
2004-03-24 19:59 ` David S. Miller
2004-02-27 20:31 Sridhar Samudrala
2004-02-27 21:38 ` David S. Miller
2004-02-27 21:44 ` Jeff Garzik
2004-02-27 22:52 ` Sridhar Samudrala
2004-02-28 23:49 ` David S. Miller
2004-02-14 0:07 Sridhar Samudrala
2004-02-14 5:54 ` 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=20040406135231.63608955.davem@redhat.com \
--to=davem@redhat.com \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=sri@us.ibm.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).