From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/7] Enable L2 cache support on Exynos4210/4x12 SoCs
Date: Fri, 28 Nov 2014 12:11:38 +0100 [thread overview]
Message-ID: <3059840.P4aX5Il9dy@wuerfel> (raw)
In-Reply-To: <54783899.2060604@samsung.com>
On Friday 28 November 2014 09:55:53 Marek Szyprowski wrote:
> On 2014-11-27 23:51, Russell King - ARM Linux wrote:
> > On Mon, Nov 17, 2014 at 12:48:22PM +0100, Marek Szyprowski wrote:
> >>
> >> Changes in this version tested on Exynos4412-based TRATS2 and OdroidU3+
> >> boards (both with secure firmware). There should be no functional change
> >> for Exynos boards running without secure firmware. I do not have access
> >> to affected non-Exynos boards, so I could not test on them.
> > So, I applied this series, and now I get a conflicts between my tree and
> > arm-soc for:
> >
> > arch/arm/mach-exynos/firmware.c
> > arch/arm/mach-exynos/sleep.S
> >
> > So, I'm going to un-stage the exynos bits, and we'll have to work out
> > some way to handle those.
Ok
> I've already pointed that those patches depend on other previously merged to
> exynos and arm-soc trees, but both Arnd and Kukjin said that those patch
> series
> should go via your kernel tree:
>
> https://lkml.org/lkml/2014/11/15/158
>
> That's why in v9 I rebased patches once again onto vanilla v3.18-rc4 and
> uploaded
> to your patch tracker. I see the following two possibilities to get them
> merged:
>
> 1. Merge patches to rmk tree and resolve the merge conflict. The
> conflict IS quite
> easy to resolve - both trees, arm-soc and rmk only adds some code and
> the goal is
> simply to have both chunks added.
>
> 2. Merge the previous version (v8 from the above link) to arm-soc tree,
> where it
> applies cleanly on for-next, preferably with Russell's Acked-by.
>
> Arnd, Russell: which approach do you prefer? How can I help to get it
> merged?
I'm fine with it either way. Russell, if you like you can merge
http://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung v3.19-next/pm-samsung-2
into your tree and resolve the conflict on your end, we have a stable
copy of that branch queued in next/soc.
If you prefer v8 to go through arm-soc, that's fine with me too, or
we could share a branch with v9 of Marek's series and have that merged
into arm-soc/next/soc to resolve the conflict.
arnd
next prev parent reply other threads:[~2014-11-28 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:48 [PATCH v9 0/7] Enable L2 cache support on Exynos4210/4x12 SoCs Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 1/7] ARM: l2c: Refactor the driver to use commit-like interface Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 2/7] ARM: l2c: Add interface to ask hypervisor to configure L2C Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 3/7] ARM: l2c: Get outer cache .write_sec callback from mach_desc only if not NULL Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 4/7] ARM: l2c: Add support for overriding prefetch settings Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 5/7] ARM: EXYNOS: Add .write_sec outer cache callback for L2C-310 Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 6/7] ARM: EXYNOS: Add support for non-secure L2X0 resume Marek Szyprowski
2014-11-17 11:48 ` [PATCH v9 7/7] ARM: dts: exynos4: Add nodes for L2 cache controller Marek Szyprowski
2014-11-27 22:51 ` [PATCH v9 0/7] Enable L2 cache support on Exynos4210/4x12 SoCs Russell King - ARM Linux
2014-11-28 8:55 ` Marek Szyprowski
2014-11-28 11:11 ` Arnd Bergmann [this message]
2014-12-03 16:03 ` Russell King - ARM Linux
2014-12-03 20:26 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-11-17 11:47 Marek Szyprowski
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=3059840.P4aX5Il9dy@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