All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene@kernel.org>
To: cw00.choi@samsung.com
Cc: Chanwoo Choi <cwchoi00@gmail.com>, Kukjin Kim <kgene@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL 4/5] Samsung arm64 DT updates for v4.1
Date: Sat, 16 May 2015 12:39:21 +0900	[thread overview]
Message-ID: <5556BBE9.6030007@kernel.org> (raw)
In-Reply-To: <CAGTfZH3bzjvVLH2HALDTLUf0MzibeH7sfFJh1n=dyuitYmUw_A@mail.gmail.com>

On 05/14/15 22:56, Chanwoo Choi wrote:
> Hi Kukjin,

[...]

>> As you know, the arm64-exynos5433 couldn't be sent to upstream during
>> previous merge window because it cannot be built without other stuff
>> such as board DT file. I think, you need to post its regarding board DT
>> file, I could test the exynos5433 series in my side with smdk5433 dt
>> file though. Maybe as you know, I have no plan to upstream the smdk5433
>> DT file because it will not be used outside of Samsung S.LSI.
> 
> Thanks for your test about Exynos5433 patch-set.
> But, I cannot send the DTS file for Exynos5433 right now.
> On the next, I'll send the Exynos5433's patchset and board dts file.
> 
OK, I see. I think, maybe you can make a patch for board DT file based
on v4.2-next/dt64-samsung branch in samsung tree.

Thanks,
Kukjin

WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Samsung arm64 DT updates for v4.1
Date: Sat, 16 May 2015 12:39:21 +0900	[thread overview]
Message-ID: <5556BBE9.6030007@kernel.org> (raw)
In-Reply-To: <CAGTfZH3bzjvVLH2HALDTLUf0MzibeH7sfFJh1n=dyuitYmUw_A@mail.gmail.com>

On 05/14/15 22:56, Chanwoo Choi wrote:
> Hi Kukjin,

[...]

>> As you know, the arm64-exynos5433 couldn't be sent to upstream during
>> previous merge window because it cannot be built without other stuff
>> such as board DT file. I think, you need to post its regarding board DT
>> file, I could test the exynos5433 series in my side with smdk5433 dt
>> file though. Maybe as you know, I have no plan to upstream the smdk5433
>> DT file because it will not be used outside of Samsung S.LSI.
> 
> Thanks for your test about Exynos5433 patch-set.
> But, I cannot send the DTS file for Exynos5433 right now.
> On the next, I'll send the Exynos5433's patchset and board dts file.
> 
OK, I see. I think, maybe you can make a patch for board DT file based
on v4.2-next/dt64-samsung branch in samsung tree.

Thanks,
Kukjin

  reply	other threads:[~2015-05-16  3:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 18:39 [GIT PULL 4/5] Samsung arm64 DT updates for v4.1 Kukjin Kim
2015-05-14 13:56 ` Chanwoo Choi
2015-05-14 13:56   ` Chanwoo Choi
2015-05-16  3:39   ` Kukjin Kim [this message]
2015-05-16  3:39     ` Kukjin Kim
  -- strict thread matches above, loose matches on Subject: below --
2015-04-01 18:16 Kukjin Kim
2015-04-01 18:16 ` Kukjin Kim
2015-04-03 22:02 ` Olof Johansson
2015-04-03 22:02   ` Olof Johansson
2015-04-04  6:45   ` Kukjin Kim
2015-04-04  6:45     ` 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=5556BBE9.6030007@kernel.org \
    --to=kgene@kernel.org \
    --cc=arnd@arndb.de \
    --cc=cw00.choi@samsung.com \
    --cc=cwchoi00@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    /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.