Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Russell King - ARM Linux' <linux@arm.linux.org.uk>,
	'Arnd Bergmann' <arnd@arndb.de>
Cc: "'Jean-Christophe PLAGNIOL-VILLARD'" <plagnioj@jcrosoft.com>,
	"'Heiko Stübner'" <heiko@sntech.de>,
	"'Tushar Behera'" <tushar.behera@linaro.org>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, patches@linaro.org
Subject: RE: [PATCH 00/33] Use common macro to define resources
Date: Wed, 09 May 2012 21:55:23 +0900	[thread overview]
Message-ID: <01b201cd2de2$ffa5d7d0$fef18770$%kim@samsung.com> (raw)
In-Reply-To: <20120425113521.GW24211@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> 
> On Wed, Apr 25, 2012 at 11:21:47AM +0000, Arnd Bergmann wrote:
> > Note that the point of the DEFINE_RES_*() macros is really to prevent
> > people from coming up with new silly macros to do the same thing, as
> > we've had in the past.
> 
> One of the other reaons was to stop the stream of resources with wrong
> endings (because people kept thinking it was exclusive rather than
> inclusive) - and the resulting stream of additional patches to fix those
> errors.
> 
> The legacy platforms do have those kinds of errors - when I converted
> SA11x0 as part of a previous patch set, I found a number suffering from
> this error.  (Were any found in this patch set?  I've not read through
> it.)
> 
> I think if this becomes a small %age of the change to Samsung stuff,
> and Kukjin is happy with it, it should go in.

Yes, agree. I will apply this whole series.
Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

      parent reply	other threads:[~2012-05-09 12:55 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
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 [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='01b201cd2de2$ffa5d7d0$fef18770$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=arnd@arndb.de \
    --cc=heiko@sntech.de \
    --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