From: Stefan Wahren <stefan.wahren@i2se.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
Phil Elwell <phil@raspberrypi.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>, Eric Anholt <eric@anholt.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] irqchip/bcm2836: Move SMP startup code to arch/arm
Date: Wed, 10 May 2017 17:53:46 +0200 [thread overview]
Message-ID: <13c4ffa2-20e5-2775-ceae-e6701a5ba554@i2se.com> (raw)
In-Reply-To: <5ea27eff-8495-63d1-abd1-eef283ea2b5d@arm.com>
Am 10.05.2017 um 17:38 schrieb Marc Zyngier:
> On 10/05/17 16:32, Phil Elwell wrote:
>> On 10/05/2017 16:31, Marc Zyngier wrote:
>>> On 10/05/17 16:07, Phil Elwell wrote:
>>>> On 10/05/2017 14:32, Marc Zyngier wrote:
>>>>> On 10/05/17 14:26, Marc Zyngier wrote:
>>>>>> One of the RPi-2/3 irqchip's key features is that it contains some
>>>>>> SMP startup code for the 32bit ARM architecture version. The only
>>>>>> reason I can imagine for this is "RPi is special".
>>>>>>
>>>>>> Let's move this code where it belongs (in the platform support code),
>>>>>> creating a shared include file for this purpose.
>>>>>>
>>>>>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>>>>> Also:
>>>>> Fixes: 41f4988cc287 ("irqchip/bcm2836: Add SMP support for the 2836")
>>>>>
>>>>> M.
>>>>>
>>>> The patch has some checkpatch warnings, but otherwise:
>>> Bah...
>>>
>>> WARNING: line over 80 characters
>>> #51: FILE: arch/arm/mach-bcm/board_bcm2835.c:30:
>>> +static int bcm2836_smp_boot_secondary(unsigned int cpu, struct task_struct *idle)
>>>
>>> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
>>> #194:
>>> new file mode 100644
>>>
>>> Yup, the checkpatch stamp of approval. My screen has stopped being
>>> limited to 80 chars at some point between 1989 and 1991. As for the
>>> MAINTAINERS file, that's probably for the maintainers to pick it up.
>>>
>>>> Reviewed-by: Phil Elwell <phil@raspberrypi.org>
>>>> Tested-by: Phil Elwell <phil@raspberrypi.org>
>>> Thanks. I assume you'll respin your DSB/SEV fix on top of this?
>> Yes - how does one manage the timing of interdependent patches?
Since Phil's patch is a critical bugfix for the near future. I prefer to
have it in 4.12.
Stefan
> You get the maintainers of this code to queue both patches at the same
> time. You can take them directly through the BCM tree if that makes
> things easier for you.
>
> Thanks,
>
> M.
next prev parent reply other threads:[~2017-05-10 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 13:26 Marc Zyngier
2017-05-10 13:32 ` Marc Zyngier
2017-05-10 15:07 ` Phil Elwell
2017-05-10 15:31 ` Marc Zyngier
2017-05-10 15:32 ` Phil Elwell
2017-05-10 15:38 ` Marc Zyngier
2017-05-10 15:53 ` Stefan Wahren [this message]
2017-05-10 16:04 ` Marc Zyngier
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=13c4ffa2-20e5-2775-ceae-e6701a5ba554@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®