From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: linkwatch bustage in git-net
Date: Wed, 9 May 2007 14:11:03 -0700 [thread overview]
Message-ID: <20070509141103.9de0f654.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070509.001814.116354599.davem@davemloft.net>
On Wed, 09 May 2007 00:18:14 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> > Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> Thanks for working this out, applied and pushed to net-2.6.git
I'm all confused. I just pulled your tree and I see in the log
commit 4cba637dbb9a13706494a1c85174c8e736914010
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed May 9 00:17:30 2007 -0700
[NET] link_watch: Always schedule urgent events
and
commit fe47cdba83b3041e4ac1aa1418431020a4afe1e0
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date: Tue May 8 23:22:43 2007 -0700
[NET] link_watch: Eliminate potential delay on wrap-around
but in the actual diff and in the checked-out tree I see no sign of the
earlier patch (fe47cdba83b3041e4ac1aa1418431020a4afe1e0). I have the old
code:
/* If we wrap around we'll delay it by at most HZ. */
if (delay > HZ)
delay = 0;
where'd it go?
next prev parent reply other threads:[~2007-05-09 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:20 linkwatch bustage in git-net Andrew Morton
2007-05-09 5:31 ` Herbert Xu
2007-05-09 5:45 ` Herbert Xu
[not found] ` <20070508225153.d538f79c.akpm@linux-foundation.org>
2007-05-09 5:54 ` Herbert Xu
2007-05-09 5:58 ` Andrew Morton
2007-05-09 6:11 ` Andrew Morton
2007-05-09 6:22 ` David Miller
2007-05-09 7:16 ` Herbert Xu
2007-05-09 7:18 ` David Miller
2007-05-09 21:11 ` Andrew Morton [this message]
2007-05-09 21:39 ` David Miller
2007-05-09 21:45 ` Andrew Morton
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=20070509141103.9de0f654.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.