From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: next build: 629 warnings 1 failures (next/next-20140723)
Date: Mon, 28 Jul 2014 09:23:07 +0100 [thread overview]
Message-ID: <53D6086B.3060801@arm.com> (raw)
In-Reply-To: <20140725121411.GE24268@arm.com>
On 25/07/14 13:14, Catalin Marinas wrote:
> On Fri, Jul 25, 2014 at 12:26:23PM +0100, Jason Cooper wrote:
>> On Fri, Jul 25, 2014 at 10:01:09AM +0100, Catalin Marinas wrote:
>>> On Thu, Jul 24, 2014 at 11:48:36PM +0100, Jason Cooper wrote:
>>>> On Thu, Jul 24, 2014 at 02:24:48PM +0100, Catalin Marinas wrote:
>>>>> From 3acb8b49aeba9f48153a2d719dec05d0b862e285 Mon Sep 17 00:00:00 2001
>>>>> From: Catalin Marinas <catalin.marinas@arm.com>
>>>>> Date: Thu, 24 Jul 2014 14:14:42 +0100
>>>>> Subject: [PATCH] arm64: gicv3: Allow GICv3 compilation with older binutils
>>>>>
>>>>> GICv3 introduces new system registers accessible with the full msr/mrs
>>>>> syntax (e.g. mrs x0, Sx_op0_op1_CRm_CRn_op2). However, only recent
>>>>> binutils understand the new syntax. This patch introduces msr_s/mrs_s
>>>>> assembly macros which generate the equivalent instructions above and
>>>>> converts the existing GICv3 code (both drivers/irqchip/ and
>>>>> arch/arm64/kernel/).
>>>>>
>>>>> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
>>>>> Suggested-by: Mark Rutland <mark.rutland@arm.com>
>>>>> Reported-by: Olof Johansson <olof@lixom.net>
>>>>> Cc: Will Deacon <will.deacon@arm.com>
>>>>> Cc: Marc Zyngier <marc.zyngier@arm.com>
>>>>> ---
>>>>> arch/arm64/include/asm/sysreg.h | 60 ++++++++++++++++++++++++++++++++++++++
>>>>> arch/arm64/kernel/head.S | 6 ++--
>>>>> drivers/irqchip/irq-gic-v3.c | 16 +++++-----
>>>>> include/linux/irqchip/arm-gic-v3.h | 42 +++++++++++++-------------
>>>>> 4 files changed, 93 insertions(+), 31 deletions(-)
>>>>> create mode 100644 arch/arm64/include/asm/sysreg.h
>>>>
>>>> I'm going to assume this goes on top of Marc's series, and that you'll
>>>> take it through arm64:
>>>>
>>>> Acked-by: Jason Cooper <jason@lakedaemon.net>
>>>
>>> Thanks. I'll let Marc decide (he's back next week) as I go on holiday
>>> soon. Ideally it should go into -next and upstream together with the
>>> rest of the GICv3 patches but I (or Will if I'm way) am happy to take
>>> the patch once GICv3 hits mainline (I would like to avoid merging the
>>> irqchip tree into the arm64 tree just to be able to apply this fix).
>>
>> That's why I created a topic branch for GICv3. ;-) If you pull:
>>
>> git://git.infradead.org/users/jcooper/linux.git tags/deps-irqchip-gic-3.17
>>
>> You'll get:
>>
>> 021f653791ad irqchip: gic-v3: Initial support for GICv3
>> d51d0af43b30 irqchip: gic: Move some bits of GICv2 to a library-type file
>>
>> based on v3.16-rc1 and nothing more.
>>
>> That tag is on the irqchip/gic branch, which I'll put all the other
>> changes to gic on top of once Marc has had a chance to review them.
>>
>> The intent was for arm64 to pull the above, and apply the rest of Marc's
>> series on top. The fix just posted would go on top of that. But if you
>> want to wait...
>
> That's great, thanks. I wasn't aware (or maybe I forgot) of the plans
> for how to get GICv3 merged. I pulled the tag above and applied the fix
> on top.
Awesome. thanks for that everyone.
I'll go back moping my Inbox...
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2014-07-28 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53cf8323.e4b6440a.7d37.4f75@mx.google.com>
2014-07-23 23:27 ` next build: 629 warnings 1 failures (next/next-20140723) Olof Johansson
2014-07-24 8:50 ` Will Deacon
2014-07-24 10:43 ` Catalin Marinas
2014-07-24 13:24 ` Catalin Marinas
2014-07-24 16:08 ` Olof Johansson
2014-07-24 22:48 ` Jason Cooper
2014-07-25 9:01 ` Catalin Marinas
2014-07-25 11:26 ` Jason Cooper
2014-07-25 12:14 ` Catalin Marinas
2014-07-28 8:23 ` Marc Zyngier [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=53D6086B.3060801@arm.com \
--to=marc.zyngier@arm.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 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.