From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fbdev updates.
Date: Fri, 5 Jul 2002 19:39:23 +0100 [thread overview]
Message-ID: <20020705193923.G27920@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207051123240.25589-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Fri, Jul 05, 2002 at 11:32:51AM -0700
On Fri, Jul 05, 2002 at 11:32:51AM -0700, James Simmons wrote:
> > James, you're OTT here.
>
> I apologize I'm sorry. I did get upset. Its just this has been discussed
> time and time again. It gets annoying after awhile and it stopped me from
> completing the fbdev changes in the last development series. I don't want
> that again.
Rubbish. You posted a fbdev interface change to linux-kernel when the
kernel was supposed to be stabilising. I converted several of my drivers
to the new interface the best I could. The drivers are coded in such a
way to make the final stages of your changes as trivial as possible. I
did find a few bugs with the interface several months later, and had to
undo some of the changes. However, all work on the new interface appeared
to have stopped.
_I_ didn't stop your fbdev changes. You stopped them yourself when other
driver maintainers didn't comply with your ill-timed request. That caused
me to have to back out some of the changes.
And that's the situation today. If you want to carry on this slagging
match... but its not getting either of us anywhere.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-05 18:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:48 [PATCH] fbdev updates James Simmons
2002-07-02 13:33 ` Jani Monoses
2002-07-05 2:41 ` James Simmons
2002-07-03 23:03 ` Russell King
2002-07-05 4:05 ` James Simmons
2002-07-05 8:44 ` Russell King
2002-07-05 8:53 ` Geert Uytterhoeven
2002-07-05 9:09 ` Russell King
2002-07-05 9:39 ` Geert Uytterhoeven
2002-07-05 10:20 ` Russell King
2002-07-05 17:20 ` James Simmons
2002-07-05 17:16 ` James Simmons
2002-07-05 17:58 ` Russell King
2002-07-05 18:21 ` James Simmons
2002-07-05 18:27 ` Russell King
2002-07-05 17:14 ` James Simmons
2002-07-05 17:57 ` Russell King
2002-07-05 18:32 ` James Simmons
2002-07-05 18:39 ` Russell King [this message]
2002-07-05 19:00 ` James Simmons
2002-07-05 19:29 ` Ani Joshi
2002-07-05 19:32 ` James Simmons
2002-07-05 19:41 ` Russell King
2002-07-05 19:57 ` James Simmons
2002-07-05 19:53 ` Ani Joshi
2002-07-05 19:55 ` Ani Joshi
2002-07-05 19:58 ` James Simmons
2002-07-05 20:21 ` Ani Joshi
2002-07-05 20:09 ` James Simmons
2002-07-05 20:34 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 5:22 James Simmons
2002-07-08 21:23 James Simmons
2002-06-04 20:05 James Simmons
2002-05-28 18:09 James Simmons
2002-05-22 16:54 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=20020705193923.G27920@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).