From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Robert Schiele <rschiele@uni-mannheim.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.uni-mannheim.de: Returned mail: see transcript for details])
Date: Tue, 08 Apr 2003 15:32:45 -0600 [thread overview]
Message-ID: <3626620000.1049837565@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1049833118.8939.0.camel@dhcp22.swansea.linux.org.uk>
> On Maw, 2003-04-08 at 21:51, Robert Schiele wrote:
>> Thanks for your note. Hope you didn't feel offended. At least this was not
>> my intention. I just wanted to notify all people related to the affected
>> driver.
>>
>> So it's up to the kernel tree maintainers to bring this fix into their trees.
>
> Maintainers submit changes to the Linux kernel tree, not vice versa. Its
> push not pull
As far as the 2.4.X series is concerned, pushing has not helped. I've
seen spelling fixes and incorrorct changes get accepted from non
maintainers "instantly", while the maintainers changes are not accepted.
Considering how long it took for the last set of driver changes to make
it from -ac into kernel.org, I just assumed that this strategy was
also failing. Is that really the only way to get updates into Marcelo's
tree?
--
Justin
next prev parent reply other threads:[~2003-04-08 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 7:18 [PATCH] aic7* claims all checked EISA io ranges (was: [MAILER-DAEMON@rumms.uni-mannheim.de: Returned mail: see transcript for details]) Robert Schiele
2003-04-08 20:36 ` Justin T. Gibbs
2003-04-08 20:51 ` Robert Schiele
2003-04-08 20:18 ` Alan Cox
2003-04-08 21:32 ` Justin T. Gibbs [this message]
2003-04-09 6:01 ` Robert Schiele
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=3626620000.1049837565@aslan.btc.adaptec.com \
--to=gibbs@scsiguy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rschiele@uni-mannheim.de \
/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