netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6 PKT_SCHED]: Fix overflow on 64bit in times reported to userspace by tc actions
Date: Mon, 22 Nov 2004 12:12:27 +0100	[thread overview]
Message-ID: <41A1C99B.6010202@trash.net> (raw)
In-Reply-To: <1101059233.1093.151.camel@jzny.localdomain>

jamal wrote:

>Patrick are you going to work on the other cleanups you were thuinking
>of? ( etc)
>
I will send you a batch of patches in one or two weeks, right now I'm
waiting for you to ACK the tc_action_init patch so I can resync my
tree with Dave's.

Regards
Patrick

  reply	other threads:[~2004-11-22 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09  9:25 [PATCH 2.6 PKT_SCHED]: Fix overflow on 64bit in times reported to userspace by tc actions Patrick McHardy
2004-11-11 23:03 ` David S. Miller
2004-11-21 17:47   ` jamal
2004-11-22 11:12     ` Patrick McHardy [this message]
2004-11-22 13:24       ` jamal
2004-11-22 19:40         ` Patrick McHardy
2004-11-23 13:39           ` jamal

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=41A1C99B.6010202@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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).