From: Russell King <rmk@arm.linux.org.uk>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: James Simmons <jsimmons@transvirtual.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Linux 2.5.19
Date: Thu, 30 May 2002 00:52:07 +0100 [thread overview]
Message-ID: <20020530005207.I30585@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3CF55941.7060806@evision-ventures.com>; from dalecki@evision-ventures.com on Thu, May 30, 2002 at 12:42:09AM +0200
On Thu, May 30, 2002 at 12:42:09AM +0200, Martin Dalecki wrote:
> Well ... they have once excuse... if the maintainer is
> himself a bit slow on submitting to Linus. Yes I know that's
> a matter primary of personal style so there is no need
> to discuss about it until down...
You still don't get the point.
1. Patches from cyber2000fb.c have been submitted and the driver in Linus'
tree up to 2.5.18 is completely up to date and functional, with zero
known problems.
2. Someone comes along, scans my patch and finds a change.
3. This person takes it upon themselves to solely take that change,
and, without querying the person who put out the patch set, or
the maintainer of the driver, decides to send it to Linus without
testing it in any way since they don't have the hardware to test it.
4. Maintainer, naturally, gets really pissed off.
If you think this is acceptable, why the hell did I bother sending those
IDE DMA changes through you? After all, you don't need to know about
them because I know better than you, don't I? *That's* what you're
advocating here, and I'm sure you're going to object to that.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next prev parent reply other threads:[~2002-05-29 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020529211702.E30585@flint.arm.linux.org.uk>
2002-05-29 20:44 ` Linux 2.5.19 James Simmons
2002-05-29 20:47 ` Russell King
2002-05-29 22:22 ` Martin Dalecki
2002-05-29 23:25 ` Russell King
2002-05-29 22:42 ` Martin Dalecki
2002-05-29 23:52 ` Russell King [this message]
2002-05-29 23:00 ` Martin Dalecki
2002-05-29 22:43 ` James Simmons
2002-05-29 22:29 ` Martin Dalecki
2002-05-29 23:31 ` Russell King
2002-05-30 5:10 ` Framebuffer policy [ was Re: Linux 2.5.19] James Simmons
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=20020530005207.I30585@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dalecki@evision-ventures.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).