From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] SoCFPGA fixes for v4.6-rc5
Date: Wed, 27 Apr 2016 15:33:08 -0700 [thread overview]
Message-ID: <7h8tzyiswr.fsf@baylibre.com> (raw)
In-Reply-To: <1461684244-6112-1-git-send-email-dinguyen@kernel.org> (Dinh Nguyen's message of "Tue, 26 Apr 2016 10:24:04 -0500")
Dinh Nguyen <dinguyen@kernel•org> writes:
> Please pull in these fixes for v4.6-rc5. The first patch "ARM: SoCFPGA: Fix
> secondary CPU startup in thumb2 kernel" is a true fix for enabling CPU1 in
> thumb2 mode, but the second patch "ARM: SoCFPGA: simplify secondary trampoline"
> may not be a true fix, but it is dependent on the first patch. I didn't want
> to cause any conflicts.
IIUC, the 2nd one (simplify) seems to be dependent on the first (fix),
but doesn't seem to be appropriate for this late stage of the -rc cycle,
so I've applied the first one only. Please include the 2nd one with
your v4.7 updates.
I also verified on my socfpga board that the 2nd CPU does indeed come up
with this patch when building with THUMB2_KERNEL=y.
Thanks,
Kevin
prev parent reply other threads:[~2016-04-27 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 15:24 [GIT PULL] SoCFPGA fixes for v4.6-rc5 Dinh Nguyen
2016-04-27 22:33 ` Kevin Hilman [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=7h8tzyiswr.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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