All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/3] video: clps711x: New CLPS711X FB driver
Date: Tue, 08 Apr 2014 10:24:09 +0000	[thread overview]
Message-ID: <5343CE49.9080000@ti.com> (raw)
In-Reply-To: <1395332675-23135-1-git-send-email-shc_work@mail.ru>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On 08/04/14 13:15, Alexander Shiyan wrote:
> Tue, 8 Apr 2014 12:56:24 +0300 от Tomi Valkeinen <tomi.valkeinen@ti.com>:
>> Hi,
>>
>> On 20/03/14 18:24, Alexander Shiyan wrote:
>>> This series adds a new framebuffer driver for Cirrus Logic CLPS711X
>>> CPUs. Since all code rewritten from scratch, patch is designed as a
>>> replacement of the old (not updated for a long time) for a new one.
>>
>> Why was it rewritten from scratch? It's almost always better to improve
>> the old one, than write a new, replacing one.
> Hello.
> 
> Most of the code has been rewritten. It will be very difficult to see the changes,
> if it is presented as a patch for the old driver.

Well, now it's impossible to see the changes, except opening both files
and going through line by line. You don't even list any new features in
the description, or give any reason why a new driver is required.

And of course one huge patch changing the old driver to the new form is
bad also.

The proper way would be to gradually change the old driver with a patch
series. Then it's possible to review the patches and see what is
actually changed.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2014-04-08 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 16:24 [PATCH 0/3] video: clps711x: New CLPS711X FB driver Alexander Shiyan
2014-04-08  9:56 ` Tomi Valkeinen
2014-04-08 10:24 ` Tomi Valkeinen [this message]

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=5343CE49.9080000@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@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 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.