Thread (18 messages) flat view 18 messages, 8 authors, 2011-06-03

[PATCH v2 0/4] Move plat-mxc gpio driver into drivers/gpio

From: Grant Likely <hidden>
Date: 2011-06-03 14:56:21
Also in: lkml

On Fri, Jun 3, 2011 at 8:34 AM, Shawn Guo [off-list ref] wrote:
Hi Russell,

On Fri, Jun 03, 2011 at 08:52:01AM +0100, Russell King - ARM Linux wrote:
quoted
On Thu, Jun 02, 2011 at 11:33:48AM +0800, Shawn Guo wrote:
quoted
?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 +++++++++++++-------
quoted
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
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.
+
+static struct platform_driver mxc_gpio_driver = {
+ ? ? ? .driver ? ? ? ? = {
+ ? ? ? ? ? ? ? .name ? = "gpio-mxc",
.owner = THIS_MODULE,

g.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help