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: Ani Joshi <ajoshi@shell.unixbox.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] fbdev updates.
Date: Fri, 5 Jul 2002 20:41:07 +0100	[thread overview]
Message-ID: <20020705204107.H27920@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207051228510.30731-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Fri, Jul 05, 2002 at 12:32:57PM -0700

On Fri, Jul 05, 2002 at 12:32:57PM -0700, James Simmons wrote:
> It is and has started to got into the mainline kernel. The thing was I was
> bending over backwards to not break peoples drivers.

If it's something small, then driver people don't mind having their
drivers fixed.

However, if its something large, just break them and let the driver people
fix up the pieces (assuming you've got adequate documentation either in
code or elsewhere for people to see both the reasons for the breakage,
the direction you're heading in, and an example driver to follow.)
Chances are that they'll know their driver better than anyone else.  If
it stays broken through the next stable series, then start considering
dropping the driver.

That's how it works in the other subsystems.

(FYI, you'll probably find that most people who didn't use the fbgen layer
decided not to use it because of the fix <-> par <-> var mess it forced
into the driver design.)

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

  reply	other threads:[~2002-07-05 19:41 UTC|newest]

Thread overview: 30+ 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
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 [this message]
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

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=20020705204107.H27920@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=ajoshi@shell.unixbox.com \
    --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).