From: "Heiko Stübner" <heiko@sntech.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Tushar Behera <tushar.behera@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kgene.kim@samsung.com,
linux@arm.linux.org.uk, patches@linaro.org
Subject: Re: [PATCH 00/33] Use common macro to define resources
Date: Wed, 25 Apr 2012 09:38:57 +0200 [thread overview]
Message-ID: <201204250938.58397.heiko@sntech.de> (raw)
In-Reply-To: <20120425041939.GL9142@game.jcrosoft.org>
Hi,
Am Mittwoch, 25. April 2012, 06:19:39 schrieb Jean-Christophe PLAGNIOL-
VILLARD:
> On 09:42 Wed 25 Apr , Tushar Behera wrote:
> > There are some helper macros (DEFINE_RES_XXX) for defining resource
> > structures. This patchset migrates all the earlier resource
> > definitions (within Samsung specific code base) to use these macros.
> >
> > In some cases, it was not possible to use DEFINE_RES_IRQ() macro because
> > of usage of additional flags. In those cases, DEFINE_RES_NAMED() macro
> > is used instead.
> >
> > The patches are rebased on top of Kukjin's for-next branch at this
> > commit.
> >
> > d0ee53a Merge branch 'next/board-samsung' into for-next
>
> is this really necessary as we switch to DT this code will be droped
As far as I know legacy SoCs are allowed to keep being non-DT and I don't see
the older Samsung SoCs (especially the S3C24XX ones) changing to DT anytime
soon, as they don't see any new development but only bug fixes currently.
> for my point of view it's cosmetics change
it is, but it also makes the code more readable
Heiko
next prev parent reply other threads:[~2012-04-25 7:39 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 4:12 [PATCH 00/33] Use common macro to define resources Tushar Behera
2012-04-25 4:12 ` [PATCH 01/33] ARM: SAMSUNG: devs: " Tushar Behera
2012-04-25 4:12 ` [PATCH 02/33] ARM: EXYNOS: dev-ahci: " Tushar Behera
2012-04-25 4:12 ` [PATCH 03/33] ARM: EXYNOS: dev-audio: " Tushar Behera
2012-04-25 4:12 ` [PATCH 04/33] ARM: EXYNOS: mach-armlex4210: " Tushar Behera
2012-04-25 4:12 ` [PATCH 05/33] ARM: EXYNOS: mach-smdkv310: " Tushar Behera
2012-04-25 4:12 ` [PATCH 06/33] ARM: S3C24XX: dev-uart: " Tushar Behera
2012-04-25 9:13 ` Heiko Stübner
2012-05-08 18:40 ` [PATCH v2 " Heiko Stübner
2012-05-09 12:44 ` Kukjin Kim
2012-04-25 4:12 ` [PATCH 07/33] ARM: S3C24XX: bast-ide: " Tushar Behera
2012-04-25 4:12 ` [PATCH 08/33] ARM: S3C24XX: mach-amlm5900: " Tushar Behera
2012-04-25 4:12 ` [PATCH 09/33] ARM: S3C24XX: mach-anubis: " Tushar Behera
2012-04-25 4:12 ` [PATCH 10/33] ARM: S3C24XX: mach-at2440evb: " Tushar Behera
2012-04-25 4:12 ` [PATCH 11/33] ARM: S3C24XX: mach-bast: " Tushar Behera
2012-04-25 4:12 ` [PATCH 12/33] ARM: S3C24XX: mach-gta02: " Tushar Behera
2012-04-25 4:12 ` [PATCH 13/33] ARM: S3C24XX: mach-h1940: " Tushar Behera
2012-04-25 4:12 ` [PATCH 14/33] ARM: S3C24XX: mach-mini2440: " Tushar Behera
2012-04-25 4:12 ` [PATCH 15/33] ARM: S3C24XX: mach-nexcoder: " Tushar Behera
2012-04-25 4:12 ` [PATCH 16/33] ARM: S3C24XX: mach-osiris: " Tushar Behera
2012-04-25 16:53 ` Sergei Shtylyov
2012-04-26 3:22 ` Tushar Behera
2012-04-25 4:12 ` [PATCH 17/33] ARM: S3C24XX: mach-otom: " Tushar Behera
2012-04-25 4:12 ` [PATCH 18/33] ARM: S3C24XX: mach-qt2410: " Tushar Behera
2012-04-25 16:51 ` Sergei Shtylyov
2012-04-26 3:19 ` Tushar Behera
2012-04-25 4:12 ` [PATCH 19/33] ARM: S3C24XX: mach-rx1950: " Tushar Behera
2012-04-25 4:12 ` [PATCH 20/33] ARM: S3C24XX: mach-tct_hammer: " Tushar Behera
2012-04-25 4:12 ` [PATCH 21/33] ARM: S3C24XX: mach-vr1000: " Tushar Behera
2012-04-25 4:12 ` [PATCH 22/33] ARM: S3C24XX: simtec-nor: " Tushar Behera
2012-04-25 4:12 ` [PATCH 23/33] ARM: S3C64XX: dev-audio: " Tushar Behera
2012-04-25 4:12 ` [PATCH 24/33] ARM: S3C64XX: dev-uart: " Tushar Behera
2012-04-25 4:12 ` [PATCH 25/33] ARM: S3C64XX: mach-anw6410: " Tushar Behera
2012-04-25 4:12 ` [PATCH 26/33] ARM: S3C64XX: mach-crag6410: " Tushar Behera
2012-04-25 8:24 ` Mark Brown
2012-04-25 4:12 ` [PATCH 27/33] ARM: S3C64XX: mach-mini6410: " Tushar Behera
2012-04-25 4:12 ` [PATCH 28/33] ARM: S3C64XX: mach-real6410: " Tushar Behera
2012-04-25 4:12 ` [PATCH 29/33] ARM: S3C64XX: mach-smdk6410: " Tushar Behera
2012-04-25 4:12 ` [PATCH 30/33] ARM: S5P64X0: dev-audio: " Tushar Behera
2012-04-25 4:12 ` [PATCH 31/33] ARM: S5PC100: " Tushar Behera
2012-04-25 4:12 ` [PATCH 32/33] ARM: S5PV210: " Tushar Behera
2012-04-25 4:12 ` [PATCH 33/33] ARM: S5PV210: mach-smdkv210: " Tushar Behera
2012-04-25 4:19 ` [PATCH 00/33] " Jean-Christophe PLAGNIOL-VILLARD
2012-04-25 7:38 ` Heiko Stübner [this message]
2012-04-25 10:10 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-25 11:21 ` Arnd Bergmann
2012-04-25 11:35 ` Russell King - ARM Linux
2012-04-26 3:53 ` Tushar Behera
2012-05-09 12:55 ` Kukjin Kim
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=201204250938.58397.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.org \
--cc=plagnioj@jcrosoft.com \
--cc=tushar.behera@linaro.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