From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] 2nd Samsung S5PV210 DT support for v3.17
Date: Sat, 26 Jul 2014 12:08:43 +0200 [thread overview]
Message-ID: <5065930.BoSud11E6H@wuerfel> (raw)
In-Reply-To: <53D196FC.40004@samsung.com>
On Friday 25 July 2014 08:30:04 Kukjin Kim wrote:
>
> The following changes since commit a7a30232df01db886473324050d79c3122937c78:
>
> Merge branch 'v3.17-next/cleanup-samsung' into v3.17-next/dt-s5pv210
> (2014-07-19 04:24:18 +0900)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/s5pv210-dt
>
Pulled both branches into next/soc, thanks!
Any reason why you based it on top of -rc6? It's only a minor annoyance,
so I had no reason for not pulling it, but it does make our lives slightly
easier if we don't have to update the baseline -rc.
On a related note, I have two patch sets that I meant to send out earlier.
One moves mach-s5pv210/* into mach-exynos, the other one enables
multiplatform support for s3c64xx. The s3c64xx still has some remaining
issues (debug_ll and adc), so it will have to wait for 3.18 I guess.
If you like, I can still send you the merge of s5pv210 with exynos
to take a look.
Tomasz: one bug I just found yesterday:
config DEBUG_S3C_UART0
depends on PLAT_SAMSUNG
select DEBUG_EXYNOS_UART if ARCH_EXYNOS
select DEBUG_S3C24XX_UART if ARCH_S3C24XX
select DEBUG_S5PV210_UART if ARCH_S5PV210
This won't work if you try to enable DEBUG_LL for S5PV210
in a kernel that also includes EXYNOS support. I think it
would be good to fix this for 3.17 in some way, and in the long
run merge all the different implementations into debug/samsung.S
to avoid this problem altogether.
Arnd
prev parent reply other threads:[~2014-07-26 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 23:30 [GIT PULL 2/2] 2nd Samsung S5PV210 DT support for v3.17 Kukjin Kim
2014-07-26 10:08 ` Arnd Bergmann [this message]
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=5065930.BoSud11E6H@wuerfel \
--to=arnd@arndb.de \
--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