From: Arnd Bergmann <arnd@arndb.de>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
'Thomas Abraham' <thomas.ab@samsung.com>,
'Sylwester Nawrocki' <sylvester.nawrocki@gmail.com>,
'Kyungmin Park' <kyungmin.park@samsung.com>,
'Olof Johansson' <olof@lixom.net>
Subject: Re: [PATCH RESEND] ARM: EXYNOS: no more support non-DT for EXYNOS SoCs
Date: Wed, 10 Apr 2013 14:59:07 +0200 [thread overview]
Message-ID: <201304101459.07263.arnd@arndb.de> (raw)
In-Reply-To: <516541EB.8080404@samsung.com>
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
> On 04/10/2013 12:34 PM, Kukjin Kim wrote:
> > Kukjin Kim wrote:
> >>
> >> From: Kukjin Kim <kgene.kim@samsung.com>
> >>
> >> As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
> >> supported from v3.10. This patch removes regarding files for non-DT
> >> including board files.
> >>
> >> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
>
> It looks OK to me.
Ok. I am currently rebuilding my exynos multiplatform series on top of the
branches merged yesterday, but keeping ATAGS support alive there.
Should I rebase on top of this patch instead?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: EXYNOS: no more support non-DT for EXYNOS SoCs
Date: Wed, 10 Apr 2013 14:59:07 +0200 [thread overview]
Message-ID: <201304101459.07263.arnd@arndb.de> (raw)
In-Reply-To: <516541EB.8080404@samsung.com>
On Wednesday 10 April 2013, Sylwester Nawrocki wrote:
> On 04/10/2013 12:34 PM, Kukjin Kim wrote:
> > Kukjin Kim wrote:
> >>
> >> From: Kukjin Kim <kgene.kim@samsung.com>
> >>
> >> As we discussed in mailing list, non-DT for EXYNOS SoCs will not be
> >> supported from v3.10. This patch removes regarding files for non-DT
> >> including board files.
> >>
> >> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
>
> It looks OK to me.
Ok. I am currently rebuilding my exynos multiplatform series on top of the
branches merged yesterday, but keeping ATAGS support alive there.
Should I rebase on top of this patch instead?
Arnd
next prev parent reply other threads:[~2013-04-10 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 15:02 [PATCH RESEND] ARM: EXYNOS: no more support non-DT for EXYNOS SoCs kgene.kim
2013-04-09 15:02 ` kgene.kim at gmail.com
2013-04-10 10:34 ` Kukjin Kim
2013-04-10 10:34 ` Kukjin Kim
2013-04-10 10:41 ` Sylwester Nawrocki
2013-04-10 10:41 ` Sylwester Nawrocki
2013-04-10 12:59 ` Arnd Bergmann [this message]
2013-04-10 12:59 ` Arnd Bergmann
2013-04-10 13:46 ` Sylwester Nawrocki
2013-04-10 13:46 ` Sylwester Nawrocki
2013-04-10 13:55 ` Arnd Bergmann
2013-04-10 13:55 ` Arnd Bergmann
2013-04-10 14:05 ` Kukjin Kim
2013-04-10 14:05 ` Kukjin Kim
2013-04-22 17:08 ` Kukjin Kim
2013-04-22 17:08 ` Kukjin Kim
2013-04-22 19:11 ` Arnd Bergmann
2013-04-22 19:11 ` Arnd Bergmann
2013-04-23 14:14 ` Kukjin Kim
2013-04-23 14:14 ` Kukjin Kim
2013-05-14 12:40 ` Kukjin Kim
2013-05-14 12:40 ` 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=201304101459.07263.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=s.nawrocki@samsung.com \
--cc=sylvester.nawrocki@gmail.com \
--cc=thomas.ab@samsung.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 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.