All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	"Antonino A. Daplas" <adaplas@hotpop.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Re: [PATCH] mach64 atari patch
Date: Mon, 08 Aug 2005 07:31:40 +0800	[thread overview]
Message-ID: <42F699DC.20103@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508080003360.12912@pentafluge.infradead.org>

James Simmons wrote:
> 
>> I'll also drop fbdev-dont-allow-softcursor-use-from-userland.patch as there
>> seems to be quite a bit of controversy there.
> 
> The disagreement was how much to change it at one time. Some patches where 
> just huge and did massive changes to all drivers. I wanted to break the patch 
> up into little pieces. Please apply this patch otherwise we will be stuck 
> where we are. 
> 

Please, my patch (based from Jon's) is huge because it's removing > 200 lines
and it's moving softcursor.c from drivers/video to drivers/video/console where
it belongs. But it is _not_ intrusive.  In fact, the majority of the patch consists
of a single logical change which removes the line below from each driver

- .fb_cursor = softcursor;

and removes the line below from drivers/video/Kconfig.

- select FB_SOFT_CURSOR

Our proposal aims to make complex code simpler and big code smaller. Your patch,
on the other hand, although small, introduces another flag  FB_HWCURSOR_SOFTCURSOR,
which is redundant, and adds yet another level of complexity to an already too
complex code.

I already have the patch, but I'm not pushing it yet because of an ongoing
disagreement, in courtesy to other developers such as yourself.

Tony


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-08-07 23:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07  2:27 [PATCH] mach64 atari patch James Simmons
2005-08-07 11:39 ` Geert Uytterhoeven
2005-08-07 16:46   ` Andrew Morton
2005-08-07 23:09     ` James Simmons
2005-08-07 23:31       ` Antonino A. Daplas [this message]
2005-08-07 23:48         ` Jon Smirl
2005-08-08 17:30           ` James Simmons
2005-08-08 17:56             ` Jon Smirl
2005-08-08 18:15               ` James Simmons
2005-08-08 18:34                 ` Jon Smirl
2005-08-08 18:44                   ` James Simmons
2005-08-08 19:01                     ` Jon Smirl
2005-08-08 19:07                       ` Jon Smirl
2005-08-08 23:55                 ` Antonino A. Daplas
2005-08-09  0:04         ` James Simmons
2005-08-09  0:59           ` Antonino A. Daplas
2005-08-09  1:08             ` Antonino A. Daplas
2005-08-09  8:05             ` Geert Uytterhoeven
2005-08-09  1:04           ` Jon Smirl
2005-08-12 17:47   ` James Simmons
2005-08-08 19:49 ` Alexander Kern

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=42F699DC.20103@gmail.com \
    --to=adaplas@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.