From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Heiko Stübner" <heiko@sntech.de>,
kgene.kim@samsung.com, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/5] ARM: S3C24XX: move plat-s3c24xx/irq.c into common.c
Date: Mon, 7 May 2012 19:59:21 +0000 [thread overview]
Message-ID: <201205071959.22122.arnd@arndb.de> (raw)
In-Reply-To: <201205071941.33343.heiko@sntech.de>
On Monday 07 May 2012, Heiko Stübner wrote:
> Again following the model set out by s3c64xx.
>
> As checkpatch showed a lot of style errors and warning, these got fixed too.
>
> Signed-off-by: Heiko Stueber <heiko@sntech.de>
I object on two grounds:
1. there are plans to move irq chip drivers to drivers/irqchip eventually,
so I think it makes little sense to merge the current implementation into
another file. That just makes it harder to split it out again. Better leave
the file named irq.c and just move it to the mach-s3c24xx for now.
2. You should *never* move code around and change it at the same time
if you have a choice. Instead if you discover coding style issues with
code you want to move, fix those first and then do a second patch to
move it without further changes. Otherwise it becomes very hard to
check that the coding style changes are actually correct.
The other four patches look fine to me.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] ARM: S3C24XX: move plat-s3c24xx/irq.c into common.c
Date: Mon, 7 May 2012 19:59:21 +0000 [thread overview]
Message-ID: <201205071959.22122.arnd@arndb.de> (raw)
In-Reply-To: <201205071941.33343.heiko@sntech.de>
On Monday 07 May 2012, Heiko St?bner wrote:
> Again following the model set out by s3c64xx.
>
> As checkpatch showed a lot of style errors and warning, these got fixed too.
>
> Signed-off-by: Heiko Stueber <heiko@sntech.de>
I object on two grounds:
1. there are plans to move irq chip drivers to drivers/irqchip eventually,
so I think it makes little sense to merge the current implementation into
another file. That just makes it harder to split it out again. Better leave
the file named irq.c and just move it to the mach-s3c24xx for now.
2. You should *never* move code around and change it at the same time
if you have a choice. Instead if you discover coding style issues with
code you want to move, fix those first and then do a second patch to
move it without further changes. Otherwise it becomes very hard to
check that the coding style changes are actually correct.
The other four patches look fine to me.
Arnd
next prev parent reply other threads:[~2012-05-07 19:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 17:39 [PATCH 0/5] ARM: S3C24XX: move the easy parts to mach-s3c24xx from plat-s3c24xx Heiko Stübner
2012-05-07 17:39 ` Heiko Stübner
2012-05-07 17:40 ` [PATCH 1/5] ARM: S3C24XX: move plat-s3c24xx/cpu.c Heiko Stübner
2012-05-07 17:40 ` Heiko Stübner
2012-05-07 17:41 ` [PATCH 2/5] ARM: S3C24XX: move plat-s3c24xx/irq.c into common.c Heiko Stübner
2012-05-07 17:41 ` Heiko Stübner
2012-05-07 19:59 ` Arnd Bergmann [this message]
2012-05-07 19:59 ` Arnd Bergmann
2012-05-07 20:30 ` Heiko Stübner
2012-05-07 20:30 ` Heiko Stübner
2012-05-08 5:38 ` Kukjin Kim
2012-05-08 5:38 ` Kukjin Kim
2012-05-07 17:42 ` [PATCH 3/5] ARM: S3C24XX: move plat-s3c24xx/dev-uart.c " Heiko Stübner
2012-05-07 17:42 ` Heiko Stübner
2012-05-08 5:38 ` Kukjin Kim
2012-05-08 5:38 ` Kukjin Kim
2012-05-07 17:43 ` [PATCH 4/5] ARM: S3C24XX: move common power-management code to mach-s3c24xx Heiko Stübner
2012-05-07 17:43 ` Heiko Stübner
2012-05-07 17:44 ` [PATCH 5/5] ARM: S3C24XX: move common clock init into common.c Heiko Stübner
2012-05-07 17:44 ` Heiko Stübner
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=201205071959.22122.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.