From: jw schultz <jw@pegasys.ws>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.{4,5}.x] mod_timer fix for sch_cbq.c
Date: Sat, 3 May 2003 18:04:06 -0700 [thread overview]
Message-ID: <20030504010406.GC8288@pegasys.ws> (raw)
In-Reply-To: <1051973612.14504.7.camel@rth.ninka.net>
On Sat, May 03, 2003 at 07:53:32AM -0700, David S. Miller wrote:
> On Sat, 2003-05-03 at 07:16, Vinay K Nallamothu wrote:
> > Hi,
> >
> > sch_cbq.c: trivial {del,add}_timer to mod_timer conversions.
>
> Vinay, I sent you email earlier today saying that you
> need to send networking patches to the networking lists
> and to the networking maintainers.
>
> Yet, you're still shoveling these patches to lkml.
> What is the problem?
>
This looks like a timer fix that happens to be in network
code, not a network fix. Judging from the others he just
posted he is fixing/upgrading timer code.
He only CC'd the kernel list. The bug was sent to
davej@codemonkey.org.uk. You are askiing him to filter
every piddly fix to identify which group it should go to.
I sypmathize with your position but i think you are setting
up too high a barrier. When multiple poeple repeat the same
mistake it is called a systems problem and you fix the
system.
It strikes me that a filter subscribed to lkml could examine
the postings for lines like:
--- linux-2.5.68/net/sched/sch_cbq.c 2003-03-25 10:08:36.000000000 +0530
+++ linux-2.5.68-nvk/net/sched/sch_cbq.c 2003-05-03 19:29:08.000000000 +0530
and if present recognize "this is for the network list" and
send them there if the networking list isn't already
specified as a destination. Such functionality, once
created, could be expanded for other lists or individuals
that want it.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
prev parent reply other threads:[~2003-05-04 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 14:16 [PATCH 2.{4,5}.x] mod_timer fix for sch_cbq.c Vinay K Nallamothu
2003-05-03 14:53 ` David S. Miller
2003-05-04 1:04 ` jw schultz [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=20030504010406.GC8288@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@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