From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 2/2] bcm2835-soc-next-2017-08-15
Date: Thu, 17 Aug 2017 09:12:36 -0700 [thread overview]
Message-ID: <87valmgoln.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <36766926-c8d6-b768-59b6-4ff302a6a5ba@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
Florian Fainelli <f.fainelli@gmail.com> writes:
> On 08/15/2017 11:03 AM, Eric Anholt wrote:
>> The following changes since commit f29c256853b7412961d3ee80ca525bd2530573db:
>>
>> ARM: dts: bcm283x: Add 32-bit enable method for SMP (2017-08-14 20:09:44 +0200)
>>
>> are available in the git repository at:
>>
>> git://github.com/anholt/linux tags/bcm2835-soc-next-2017-08-15
>>
>> for you to fetch changes up to 067b437e55a892e3ebb13e40c98825fcfa1e2d99:
>>
>> ARM: bcm2836: Send event when onlining other cores (2017-08-15 10:52:26 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request brings in two things.
>>
>> One is to use sev() to wake up CPUs that might be sleeping when doing
>> the custom spin-table boot process in 32-bit mode (new firmware
>> versions will have the CPUs sleeping waiting for an event instead of
>> just spinning). However, the irqchip maintainer objected to our SMP
>> code continuing to live in the driver, so we had to move it to
>> platsmp.c, and to do that we needed a new SMP enable-method to the DT
>> for the platsmp.c to attach to (thus the DT cross-merge in this PR).
>> The platsmp.c patch was acked by irqchip for going through arm-soc.
>
> This does make us pull quite a lot of changes, how about I just
> cherry-pick "ARM: dts: bcm283x: Add 32-bit enable method for SMP" such
> that the branch in itself is functional as-is, but we don't pull in
> everything else from devicetree/next?
Then you get the commit duplicated in the history, which people
generally dislike even more. Also, it depends on the arm64->arm move,
so you'd need that as well.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-17 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 18:03 [GIT PULL 1/2] bcm2835-dt-next-2017-08-15 Eric Anholt
2017-08-15 18:03 ` [GIT PULL 2/2] bcm2835-soc-next-2017-08-15 Eric Anholt
2017-08-17 1:26 ` Florian Fainelli
2017-08-17 16:12 ` Eric Anholt [this message]
2017-08-17 18:41 ` Florian Fainelli
2017-08-17 1:11 ` [GIT PULL 1/2] bcm2835-dt-next-2017-08-15 Florian Fainelli
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=87valmgoln.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
/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
Powered by JetHome