linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: 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: Wed, 29 May 2002 21:47:39 +0100	[thread overview]
Message-ID: <20020529214739.F30585@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10205291331500.19493-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Wed, May 29, 2002 at 01:44:12PM -0700

On Wed, May 29, 2002 at 01:44:12PM -0700, James Simmons wrote:
> > This is completely wrong - the driver has been tested NOT to work on
> > the Integraphics 1682.  As such, please do uncomment these lines.
> 
> Due to a error with merging some stuff from a older DJ tree. I fixed it
> in the fbdev BK repository.

They haven't *been* in any DJ tree.

> > In addition, I'm disappointed that no one forwarded the patch for
> > maintainer approval PRIOR to submitting it to Linus.
> 
> I'm even more disappointed that some people DONT test my patches especially
> when I announce them and usually wait about 5 days before pushing them to 
> Linus. Some of the changes I have done have been sitting around for months
> in the DJ tree. The good news is that people can now look at skeletonfb.c
> to see how to port the fbdev drivers to the new api. Of course I have a
> feeling most will not bother so I will have to do it for them.

Why the fuck should I go around finding and testing peoples trees when I
haven't submitted the stuff to them?  *YOU* shouldn't go around randomly
pulling stuff from maintainers trees without first asking them why the
change hasn't been submitted.

I'm not talking about general maintainence of the cyber2000fb driver here,
or general "keep it working" type changes.  I'm talking about a blatent
"take the version from the rmk patch and submit it to Linus without telling
the maintainer of the code you're buggering with" attitude here.

-- 
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

  reply	other threads:[~2002-05-29 20:47 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 [this message]
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
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=20020529214739.F30585@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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).