linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Move plat-mxc gpio driver into drivers/gpio
Date: Fri, 3 Jun 2011 09:48:00 -0600	[thread overview]
Message-ID: <BANLkTi=odpKzvkFfhdbinH3j8-Omz9HM2g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=-YdaU07TrJsbJuZ9SrYi9uV0ACQ@mail.gmail.com>

On Fri, Jun 3, 2011 at 9:47 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Jun 3, 2011 at 9:26 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
>> Hi Grant,
>>
>> On Fri, Jun 03, 2011 at 08:55:58AM -0600, Grant Likely wrote:
>>> On Fri, Jun 3, 2011 at 8:34 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
>>> > Hi Russell,
>>> >
>>> > On Fri, Jun 03, 2011 at 08:52:01AM +0100, Russell King - ARM Linux wrote:
>>> >> On Thu, Jun 02, 2011 at 11:33:48AM +0800, Shawn Guo wrote:
>>> >> > ?arch/arm/plat-mxc/gpio.c ? ? ? ? ? ? ? ? ? ? ? ?| ?361 -------------------
>>> >> > ?drivers/gpio/gpio-mxc.c ? ? ? ? ? ? ? ? ? ? ? ? | ?433 +++++++++++++++++++++++
>>> >>
>>> > My bad here. ?I should have used 'git diff --stat -M' to show the
>>> > the following.
>>> >
>>> > .../arm/plat-mxc/gpio.c => drivers/gpio/gpio-mxc.c | ?216 +++++++++++++-------
>>> >
>>> >> I'm wondering why just moving this driver into drivers/gpio has
>>> >> resulted in it growing by 72 lines - and it's not clear from the
>>> >> diffs why that is because of the way they're broken up.
>>> >>
>>> > Yes, I agree. ?But when I did something like that to ease the review,
>>> > people think it's not necessary :)
>>> >
>>> > http://permalink.gmane.org/gmane.linux.kernel/1143257
>>>
>>> The issue was bisectability: it looked like the build would break
>>> after applying the first patch. ?The first patch should move the
>>
>> Yes, the build would break only if you change Kconfig/Makefile to
>> actually build it. ?The patch does not enable the build of the driver
>> in the patch.
>>
>>> driver without breaking the build, and then you can follow up with
>>> driver fixes. ?I don't want to see functional changes mixed in with
>>> the file move change.
>>>
>> Understood. ?Do you want me to resend the gpio-mxs and gpio-mxc patch
>> sets for that? ?Or can I follow the practice you and Russell
>> suggested in the future posts? ?I have learnt the lesson.
>
> Please repost.

An you can add in any acked-by you've received on these patches.

g.

      reply	other threads:[~2011-06-03 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02  3:33 [PATCH v2 0/4] Move plat-mxc gpio driver into drivers/gpio Shawn Guo
2011-06-02  3:33 ` [PATCH v2 1/4] gpio: gpio-mxc: add gpio driver for Freescale MXC architecture Shawn Guo
2011-06-02  5:24   ` Olof Johansson
2011-06-02  3:33 ` [PATCH v2 2/4] ARM: mxc: migrate mach-mx5 gpio driver to gpio-mxc Shawn Guo
2011-06-02  5:18   ` Olof Johansson
2011-06-02  3:33 ` [PATCH v2 3/4] ARM: mxc: migrate mach-imx " Shawn Guo
2011-06-02  5:19   ` Olof Johansson
2011-06-03 10:59   ` Philippe Rétornaz
2011-06-03 11:54   ` Fabio Estevam
2011-06-03 13:23     ` Arnd Bergmann
2011-06-02  3:33 ` [PATCH v2 4/4] ARM: mxc: remove plat-mxc/gpio driver Shawn Guo
2011-06-02  5:20   ` Olof Johansson
2011-06-03  7:52 ` [PATCH v2 0/4] Move plat-mxc gpio driver into drivers/gpio Russell King - ARM Linux
2011-06-03 14:34   ` Shawn Guo
2011-06-03 14:55     ` Grant Likely
2011-06-03 15:26       ` Shawn Guo
2011-06-03 15:47         ` Grant Likely
2011-06-03 15:48           ` Grant Likely [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='BANLkTi=odpKzvkFfhdbinH3j8-Omz9HM2g@mail.gmail.com' \
    --to=grant.likely@secretlab.ca \
    --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).