From: Dmitry Torokhov <dtor_core@ameritech.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] sch_prio - fix compile warning + some logic rearrangement in enqueue
Date: Tue, 29 Jun 2004 17:26:10 -0500 [thread overview]
Message-ID: <200406291726.10294.dtor_core@ameritech.net> (raw)
In-Reply-To: <1088547379.1039.0.camel@jzny.localdomain>
On Tuesday 29 June 2004 05:16 pm, jamal wrote:
>
> On Tue, 2004-06-29 at 17:50, David S. Miller wrote:
>
> > Should I back Dmitry's change out for now then?
>
> Yes please.
>
I'll be back ;) when your changes are committed.
--
Dmitry
prev parent reply other threads:[~2004-06-29 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 6:06 [PATCH] sch_prio - fix compile warning + some logic rearrangement in enqueue Dmitry Torokhov
2004-06-29 21:32 ` David S. Miller
[not found] ` <1088545330.1157.88.camel@jzny.localdomain>
2004-06-29 21:50 ` David S. Miller
2004-06-29 22:16 ` jamal
2004-06-29 22:21 ` David S. Miller
2004-06-29 22:26 ` Dmitry Torokhov [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=200406291726.10294.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=davem@redhat.com \
--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).