devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	devicetree-discuss@lists.ozlabs.org, kgene.kim@samsung.com,
	kwangwoo.lee@gmail.com, jacmet@sunsite.dk,
	augulis.darius@gmail.com, mcuelenaere@gmail.com,
	linux@arm.linux.org.uk, Rob Herring <robherring2@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v5 0/6] Initial Device Tree support for S3C64xx
Date: Tue, 16 Apr 2013 17:33:32 +0100	[thread overview]
Message-ID: <20130416163331.GP26958@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366060483-20342-1-git-send-email-tomasz.figa@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

On Mon, Apr 15, 2013 at 11:14:37PM +0200, Tomasz Figa wrote:
> This series adds Device Tree support for Samsung S3C64xx SoC series.
> 
> It fixes several problems preventing from booting an S3C64xx-based system
> using Device Tree, adds all the infrastructure for Device Tree-based board
> support, including mach-s3c64xx-dt and dts include files for S3C64xx SoCs,
> and basic device tree source for FriendlyARM Mini6410 board.

I tried to test this but the pinctrl driver doesn't build in -next
(drivers/pinctrl/pinctrl-s3c64xx.c:418:9: error: undefined identifier
'chained_irq_enter') - will check properly tomorrow, need to leave now.
But that's separate anyway. :P

Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-04-16 16:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 21:14 [PATCH v5 0/6] Initial Device Tree support for S3C64xx Tomasz Figa
2013-04-15 21:14 ` [PATCH v5 1/6] ARM: common: vic: Parse interrupt and resume masks from device tree Tomasz Figa
2013-04-15 21:14 ` [PATCH v5 2/6] ARM: s3c64xx: Skip legacy EINT setup if pinctrl-s3c64xx driver is present Tomasz Figa
2013-04-16 16:26   ` Mark Brown
2013-04-16 22:31     ` Tomasz Figa
2013-04-16 22:43     ` [PATCH v6 " Tomasz Figa
2013-04-15 21:14 ` [PATCH v5 3/6] gpio: samsung: Skip legacy GPIO registration if pinctrl-s3c64xx " Tomasz Figa
2013-04-16 16:27   ` Mark Brown
2013-04-16 22:35     ` Tomasz Figa
2013-04-17 13:06       ` Mark Brown
2013-04-23 14:33         ` Kukjin Kim
2013-04-15 21:14 ` [PATCH v5 4/6] ARM: s3c64xx: Add board file for boot using Device Tree Tomasz Figa
2013-04-15 21:14 ` [PATCH v5 5/6] ARM: dts: Add basic dts include files for Samsung S3C64xx SoCs Tomasz Figa
2013-04-16 13:09   ` Rob Herring
2013-04-16 13:19     ` Tomasz Figa
2013-04-17 17:46       ` Rob Herring
2013-04-23 14:29         ` Kukjin Kim
2013-04-23 14:44           ` Tomasz Figa
2013-04-23 14:48             ` Kukjin Kim
2013-04-15 21:14 ` [PATCH v5 6/6] ARM: dts: Add dts file for S3C6410-based Mini6410 board Tomasz Figa
2013-04-16 16:33 ` Mark Brown [this message]
2013-04-16 22:23   ` [PATCH 1/2] pinctrl: s3c64xx: Fix build error caused by undefined chained_irq_enter Tomasz Figa
2013-04-16 22:24     ` [PATCH 2/2] pinctrl: samsung: Fix link error with CONFIG_PINCTRL_EXYNOS disabled Tomasz Figa
2013-04-23 12:03       ` Linus Walleij
2013-04-23 12:09         ` Tomasz Figa
2013-04-24 14:27           ` Linus Walleij
2013-04-24 14:47             ` Tomasz Figa
2013-04-25 13:26               ` Linus Walleij
2013-04-16 22:29     ` [PATCH RESEND " Tomasz Figa
2013-04-23 12:00     ` [PATCH 1/2] pinctrl: s3c64xx: Fix build error caused by undefined chained_irq_enter Linus Walleij
2013-04-17 13:08 ` [PATCH v5 0/6] Initial Device Tree support for S3C64xx Mark Brown

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=20130416163331.GP26958@opensource.wolfsonmicro.com \
    --to=broonie@kernel.org \
    --cc=augulis.darius@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jacmet@sunsite.dk \
    --cc=kgene.kim@samsung.com \
    --cc=kwangwoo.lee@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mcuelenaere@gmail.com \
    --cc=robherring2@gmail.com \
    --cc=tomasz.figa@gmail.com \
    /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).