From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 0/5] Support new Exynos3250 SoC based on Cortex-A7 dual core
Date: Mon, 19 May 2014 13:39:23 +0200 [thread overview]
Message-ID: <5379ED6B.8060309@gmail.com> (raw)
In-Reply-To: <5379ECBF.9010706@gmail.com>
On 19.05.2014 13:36, Tomasz Figa wrote:
> Hi Kukjin, Chanwoo,
>
> On 15.05.2014 06:28, Chanwoo Choi wrote:
>> Dear Kukjin,
>>
>> Could you please pick following patches?
>> - [PATCHv5 1/5] ARM: EXYNOS: Add Exynos3250 SoC ID
>> - [PATCHv5 2/5] ARM: EXYNOS: Support secondary CPU boot of Exynos3250
>
> I'd say that [PATCHv5 5/5] ARM: dts: Add device tree sources for
> Exynos3250 would be also useful. :)
Aha, it is already applied. I should have checked in the tree first. Sorry.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-05-19 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 13:05 [PATCHv5 0/5] Support new Exynos3250 SoC based on Cortex-A7 dual core Chanwoo Choi
2014-05-13 13:05 ` [PATCHv5 1/5] ARM: EXYNOS: Add Exynos3250 SoC ID Chanwoo Choi
2014-05-13 13:05 ` [PATCHv5 2/5] ARM: EXYNOS: Support secondary CPU boot of Exynos3250 Chanwoo Choi
2014-05-14 19:32 ` Tomasz Figa
2014-05-13 13:05 ` [PATCHv5 3/5] clk: samsung: exynos3250: Add clocks using common clock framework Chanwoo Choi
2014-05-14 19:31 ` Tomasz Figa
2014-05-13 13:05 ` [PATCHv5 4/5] dt-bindings: add documentation for Exynos3250 clock controller Chanwoo Choi
2014-05-14 19:35 ` Tomasz Figa
2014-05-14 19:46 ` Kukjin Kim
2014-05-14 19:54 ` Tomasz Figa
2014-05-13 13:05 ` [PATCHv5 5/5] ARM: dts: Add device tree sources for Exynos3250 Chanwoo Choi
2014-05-14 19:36 ` Tomasz Figa
2014-05-15 4:28 ` [PATCHv5 0/5] Support new Exynos3250 SoC based on Cortex-A7 dual core Chanwoo Choi
2014-05-19 11:36 ` Tomasz Figa
2014-05-19 11:39 ` Tomasz Figa [this message]
2014-05-19 15: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=5379ED6B.8060309@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).