From: David Miller <davem@davemloft.net>
To: jarkao2@gmail.com
Cc: jhhwang@os.korea.ac.kr, netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: for tcp westwood implementation
Date: Sun, 03 Jan 2010 22:19:49 -0800 (PST) [thread overview]
Message-ID: <20100103.221949.102909332.davem@davemloft.net> (raw)
In-Reply-To: <20091228123202.GA8435@ff.dom.local>
From: Jarek Poplawski <jarkao2@gmail.com>
Date: Mon, 28 Dec 2009 12:32:02 +0000
> On Mon, Dec 28, 2009 at 07:52:23PM +0900, Jae-Hyun Hwang wrote:
>> Is it still wrong?
>> I hope this patch is successful.
>
> I hope too, but it depends on David. This time it's mostly OK, execept
> "Content-Transfer-Encoding: quoted-printable" instead of "inline", as
> required by Documentation/SubmittingPatches.
Patchwork didn't pick it up either, it definitely needs to be
resent.
next prev parent reply other threads:[~2010-01-04 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 6:35 [PATCH] tcp: for tcp westwood implementation Jae-Hyun Hwang
2009-12-28 8:43 ` Jarek Poplawski
2009-12-28 10:52 ` Jae-Hyun Hwang
2009-12-28 12:32 ` Jarek Poplawski
2010-01-04 6:19 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-28 5:18 Hwang Jae-Hyun
2009-12-28 5:56 ` 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=20100103.221949.102909332.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jarkao2@gmail.com \
--cc=jhhwang@os.korea.ac.kr \
--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).