netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jamal <hadi@cyberus.ca>
Cc: "Dimitry V. Ketov" <Dimitry.Ketov@avalon.ru>,
	netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
	"Alexey N. Kuznetsov" <kuznet@ms2.inr.ac.ru>
Subject: Re: [PATCH] [2.4.20] filter_list destroy fix in net/sched/sch_prio.c
Date: 12 Apr 2003 00:32:05 -0700	[thread overview]
Message-ID: <1050132725.13106.2.camel@rth.ninka.net> (raw)
In-Reply-To: <20030410135727.M86925@shell.cyberus.ca>

On Thu, 2003-04-10 at 10:57, jamal wrote:
> Looks good to me.

He missed sch_csz.c, I already sent a patch I wrote for this
to Linus and Marcelo will get a copy soon'ish.

-- 
David S. Miller <davem@redhat.com>

      reply	other threads:[~2003-04-12  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 17:46 [PATCH] [2.4.20] filter_list destroy fix in net/sched/sch_prio.c Dimitry V. Ketov
2003-04-10 17:57 ` jamal
2003-04-12  7:32   ` David S. Miller [this message]

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=1050132725.13106.2.camel@rth.ninka.net \
    --to=davem@redhat.com \
    --cc=Dimitry.Ketov@avalon.ru \
    --cc=hadi@cyberus.ca \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --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).