Linux SPI subsystem development
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work-JGs/UdohzUI@public.gmane.org>
To: "Mark Brown" <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] spi: clps711x: Driver refactor
Date: Wed, 01 Jan 2014 17:44:11 +0400	[thread overview]
Message-ID: <1388583851.810843204@f301.i.mail.ru> (raw)
In-Reply-To: <20140101132334.GP31886-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

Hello.

> On Wed, Jan 01, 2014 at 10:09:28AM +0400, Alexander Shiyan wrote:
> > This is a complex patch for refactoring CLPS711X SPI driver.
> > Major changes:
> > - Eliminate <mach/hardware.h> usage.
> > - Devicetree support.
> 
> This really needs to be broken up into smaller changes so it can be
> reviewed, your summary would be good as the cover mail for a patch
> series but not for a single commit.  We need one change per commit with
> a clear commit message saying what's going on.
> 
> There's a large set of changes here with no explanation of most of them
> which means I can't really tell if the changes are doing what they're
> supposed to and at least some of them seem to be doing things beyond
> either description above.  I'd expect at least two changes, one for the
> mach/hardware.h elimination and one for the bindings, but probably each
> of those should be split into several changes.  For example the bindings
> changes might have some patches doing refactorings before adding the
> actual bindings.

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.
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? 
Thanks.

---

  parent reply	other threads:[~2014-01-01 13:44 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
     [not found] ` <1388556568-10973-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2014-01-01 13:23   ` Mark Brown
     [not found]     ` <20140101132334.GP31886-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-01 13:44       ` Alexander Shiyan [this message]
     [not found]         ` <1388583851.810843204-7YUp6uTCZANsdVUOrk1QfQ@public.gmane.org>
2014-01-01 15:07           ` Mark Brown
     [not found]             ` <20140101150737.GR31886-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-02 17:46               ` Arnd Bergmann
2014-01-02 18:20                 ` Alexander Shiyan
     [not found]                 ` <201401021846.23488.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-02 18:25                   ` Mark Brown
     [not found]                     ` <20140102182549.GF31886-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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=1388583851.810843204@f301.i.mail.ru \
    --to=shc_work-jgs/udohzui@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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