From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: me@jayr.de, netdev@vger.kernel.org
Subject: Re: PATCH: ipv6: avoid wraparound for expired lifetimes
Date: Thu, 25 Jun 2009 01:42:32 -0700 (PDT) [thread overview]
Message-ID: <20090625.014232.100502679.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0906251135410.917@melkinkari.cs.Helsinki.FI>
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Thu, 25 Jun 2009 11:40:19 +0300 (EEST)
> On Thu, 25 Jun 2009, Jens Rosenboom wrote:
>
>> the following patch
>> should fix this, at least it did in the test I ran.
>
> You must be kidding...
Jens, don't even bother posting patches that fail to
build.
And if you can't get your patches straight, and the
problem is that you're sending something other than
what you actually tested, that's _MUCH_ worse.
next prev parent reply other threads:[~2009-06-25 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 7:39 PATCH: ipv6: avoid wraparound for expired lifetimes Jens Rosenboom
2009-06-25 8:40 ` Ilpo Järvinen
2009-06-25 8:42 ` David Miller [this message]
2009-06-25 9:06 ` Jens Rosenboom
2009-06-25 9:25 ` Wei Yongjun
2009-06-25 9:33 ` David Miller
2009-06-25 9:35 ` Ilpo Järvinen
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=20090625.014232.100502679.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=me@jayr.de \
--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).