From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] spi: clps711x: Driver refactor
Date: Wed, 1 Jan 2014 15:07:37 +0000 [thread overview]
Message-ID: <20140101150737.GR31886@sirena.org.uk> (raw)
In-Reply-To: <1388583851.810843204@f301.i.mail.ru>
On Wed, Jan 01, 2014 at 05:44:11PM +0400, Alexander Shiyan wrote:
> I wrote that this is a complex patch. This is not a fix, but new driver,
> many things are done differently.
> I do not see a way to separate these changes.
I already mentioned one thing that could be done incrementally (the
conversion to devm), from the glance I took through the code there's
several other things that jump out and like I said at least splitting
the hardware.h removal from the device tree changes would be a start.
Nothing in what you said the change did nor in the change itself
suggested that it would be impossible to break things up, I'm not
convinced that any attempt has been made to split anything out.
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140101/520fd267/attachment.sig>
next prev parent reply other threads:[~2014-01-01 15:07 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 [this message]
2014-01-02 17:46 ` Arnd Bergmann
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=20140101150737.GR31886@sirena.org.uk \
--to=broonie@kernel.org \
--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).