linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] spi: clps711x: Driver refactor
Date: Thu, 2 Jan 2014 18:46:23 +0100	[thread overview]
Message-ID: <201401021846.23488.arnd@arndb.de> (raw)
In-Reply-To: <20140101150737.GR31886@sirena.org.uk>

On Wednesday 01 January 2014, Mark Brown wrote:
> > As an alternative, I can create patch to remove current driver,
> > then re-adding new one.  Will be more convenient to watch. Is it better? 
> 
> No, that's really not good.  It's very rare that we just completely
> rewrite a driver especially not one that's been around for a while -
> there needs to be a really good reason for it.  This is a key part of
> how the development process works, incremental improvements and code
> review.  Doing this both helps improve quality control on changes and
> allows collaboration.

I definitely agree with what you say, but please note that Alexander is
the only person who ever sends clps711x patches, so there is not much
hope of collaboration. I also suspect he's the only one who would
suffer from accidental breakage, especially since the existing driver
is not used anywhere upstream (no instance of platform data, and no
DT support).

	Arnd

  reply	other threads:[~2014-01-02 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01  6:09 [PATCH 1/2] spi: clps711x: Driver refactor Alexander Shiyan
2014-01-01 13:23 ` Mark Brown
2014-01-01 13:44   ` Alexander Shiyan
2014-01-01 15:07     ` Mark Brown
2014-01-02 17:46       ` Arnd Bergmann [this message]
2014-01-02 18:20         ` Alexander Shiyan
2014-01-02 18:25         ` Mark Brown
2014-01-02 19:03           ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2016-07-06 14:53 Arnd Bergmann

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=201401021846.23488.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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).