From: Minkyu Kang <mk7.kang@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/3] EXYNOS: Add support for Exynos4x12
Date: Fri, 07 Dec 2012 16:49:56 +0900 [thread overview]
Message-ID: <50C19FA4.6060804@samsung.com> (raw)
In-Reply-To: <CANuQgHHLmb=LRnm5DFx989EZMX5np3zJ_qj+Kbf3oS5Xy1Xi1g@mail.gmail.com>
Dear Chander,
On 02/11/12 19:51, Chander Kashyap wrote:
> ping
>
> On 2 October 2012 15:16, Chander Kashyap <chander.kashyap@linaro.org> wrote:
>> This patch series popultes Register addresses, clock structure and
>> gpio structure for Exynos4x12.
>>
>> Changes in v2:
>> - Fixed the GPIO base address macro for exynos4x12_gpio_part3_get_nr
>> in arch/arm/include/asm/arch-exynos/gpio.h
>> Chander Kashyap (3):
>> EXYNOS: EXYNOS4X12: Populate Exynos4x12 register addresses
>> EXYNOS: EXYNOS4X12: Add clock structure for EXYNOS4X12
>> EXYNOS: EXYNOS4X12: Add gpio structure for EXYNOS4X12
>>
>> arch/arm/include/asm/arch-exynos/clock.h | 276 ++++++++++++++++++++++++++++++
>> arch/arm/include/asm/arch-exynos/cpu.h | 48 +++++-
>> arch/arm/include/asm/arch-exynos/gpio.h | 85 +++++++++
>> 3 files changed, 402 insertions(+), 7 deletions(-)
>>
Patches are looks good.
Please rebase this patchset.
Thanks.
Minkyu Kang.
next prev parent reply other threads:[~2012-12-07 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:16 [U-Boot] [PATCH v2 0/3] EXYNOS: Add support for Exynos4x12 Chander Kashyap
2012-10-02 13:16 ` [U-Boot] [PATCH v2 1/3] EXYNOS: EXYNOS4X12: Populate Exynos4x12 register addresses Chander Kashyap
2012-10-02 13:16 ` [U-Boot] [PATCH v2 2/3] EXYNOS: EXYNOS4X12: Add clock structure for EXYNOS4X12 Chander Kashyap
2012-10-02 13:16 ` [U-Boot] [PATCH v2 3/3] EXYNOS: EXYNOS4X12: Add gpio " Chander Kashyap
2012-10-03 0:16 ` [U-Boot] [PATCH v2 0/3] EXYNOS: Add support for Exynos4x12 Marek Vasut
2012-10-03 5:34 ` Chander Kashyap
2012-10-03 5:53 ` Viresh Kumar
2012-11-02 10:51 ` Chander Kashyap
2012-11-02 14:33 ` Marek Vasut
2012-12-07 7:49 ` Minkyu Kang [this message]
2012-12-07 7:55 ` Chander Kashyap
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=50C19FA4.6060804@samsung.com \
--to=mk7.kang@samsung.com \
--cc=u-boot@lists.denx.de \
/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