All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Lewandowski <k.lewandowsk@samsung.com>
To: kgene.kim@samsung.com
Cc: thomas.abraham@linaro.org, m.szyprowski@samsung.com,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	kyungmin.park@samsung.com
Subject: Re: [PATCH] ARM: Exynos4: Bring exynos4-dt up to date
Date: Thu, 09 Feb 2012 10:24:32 +0100	[thread overview]
Message-ID: <4F3390D0.7040209@samsung.com> (raw)
In-Reply-To: <1328028434-30139-2-git-send-email-k.lewandowsk@samsung.com>

On 31.01.2012 17:47, Karol Lewandowski wrote:

> This commit brings exynos4-dt in line with recent changes to
> mach-exynos tree, specifically:
> 
>  - Fixes build break related to replacing plat/exynos4.h with common.h
>    in commit cc511b8d84d8 ("ARM: 7257/1: EXYNOS: introduce
>    arch/arm/mach-exynos/common.[ch]")


 
>  - Converts machine to use CONFIG_MULTI_IRQ_HANDLER as done for other
>    machines in commit 4e44d2cb95bd ("ARM: exynos4: convert to
>    CONFIG_MULTI_IRQ_HANDLER") converted all exynos boards but
>    exynos4-dt.c.


Minor correction - text from "converted all.." shall be deleted, like:

   - Converts machine to use CONFIG_MULTI_IRQ_HANDLER as done for other
     machines in commit 4e44d2cb95bd ("ARM: exynos4: convert to
     CONFIG_MULTI_IRQ_HANDLER")

(It's result of not proofreading it carefully enough after squashing all
the patches.)

I don't think such a change is worth sending patch again, but I would be
grateful if you could fix it while merging.

Thanks

-- 
Karol Lewandowski | Samsung Poland R&D Center | Linux/Platform

  reply	other threads:[~2012-02-09  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 16:47 [PATCH v2] EXYNOS4_DT fixes for 3.3-rc1+ kernels Karol Lewandowski
2012-01-31 16:47 ` [PATCH] ARM: Exynos4: Bring exynos4-dt up to date Karol Lewandowski
2012-02-09  9:24   ` Karol Lewandowski [this message]
2012-02-09 10:23     ` Kukjin Kim
2012-02-09 10:23   ` 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=4F3390D0.7040209@samsung.com \
    --to=k.lewandowsk@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=thomas.abraham@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 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.