public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Dave Jones <davej@suse.de>
Cc: Steven Walter <srwalter@yahoo.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] unchecked request_region's in drivers/net
Date: Thu, 27 Dec 2001 20:51:41 -0200	[thread overview]
Message-ID: <20011227205141.C30930@conectiva.com.br> (raw)
In-Reply-To: <20011227202345.B30930@conectiva.com.br> <Pine.LNX.4.33.0112272332540.15706-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0112272332540.15706-100000@Appserv.suse.de>

Em Thu, Dec 27, 2001 at 11:44:12PM +0100, Dave Jones escreveu:
> On Thu, 27 Dec 2001, Arnaldo Carvalho de Melo wrote:
> 
> > > Patch is against kernel 2.4.17, should apply to 2.5 as well.
> > Good job! But please consider splitting the patch per driver and sending it
> > to the respective maintainers.
> 
> Someone with far too much time on their hands would be my personal
> hero[*] if they were to write a script (in language of their choice) to
> parse a diff, extract filename, and do lookup in a flat text file
> to find a list of maintainers/interested parties.

Humm, wouldn't it be the case to update MAINTAINERS? Or having something
like another file INTERESTED or other better name with addresses of the
right person/mailing list to send patches to?

But I like the idea of a web interface so that people interested in
specific drivers/files could register and receive it when patches are
submitted, maybe this can be coupled with the patchbot idea, that would
lookup this database (plain text file, don't worry) and send the message to
the interested people.

/me thinks... I think we have this in our linux distribution buildsystem,
for people to register interest in particular packages, but that may well
be coupled with bugzilla, and that would be too much for this simple
system... ok, I'll look into this with the distro folks here.

- Arnaldo

  reply	other threads:[~2001-12-27 22:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 20:38 [RFC][PATCH] unchecked request_region's in drivers/net Steven Walter
2001-12-27 22:23 ` Arnaldo Carvalho de Melo
2001-12-27 22:44   ` Dave Jones
2001-12-27 22:51     ` Arnaldo Carvalho de Melo [this message]
2001-12-27 23:25     ` James A Sutherland
2001-12-27 23:40       ` Dave Jones
2001-12-28  9:50         ` James A Sutherland
2001-12-28 11:14           ` Dave Jones
2001-12-27 23:31     ` Andreas Dilger
2001-12-27 23:40       ` Arnaldo Carvalho de Melo
2001-12-28  0:11         ` Andreas Dilger
2001-12-28  0:25           ` Arnaldo Carvalho de Melo
2001-12-27 23:51       ` Dave Jones
2001-12-28  0:14         ` Andreas Dilger
2001-12-28  0:42           ` Alan Cox
2001-12-28 18:34       ` Riley Williams
2001-12-28 18:48         ` Alan Cox
2001-12-28 19:38           ` Rik van Riel
2001-12-28 23:26             ` Alan Cox
2001-12-28 20:48           ` James A Sutherland
2001-12-28 20:34         ` Andreas Dilger
2001-12-28 21:23           ` Riley Williams
2001-12-29 18:21     ` Oliver Xymoron
  -- strict thread matches above, loose matches on Subject: below --
2001-12-28  7:21 Zwane Mwaikambo
2001-12-28 16:29 ` Alan Cox

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=20011227205141.C30930@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srwalter@yahoo.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