From: Florian Fainelli <f.fainelli@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>,
Russell King <linux@arm.linux.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 3/3] ARM: BCM5301X: remove workaround imprecise abort fault handler
Date: Tue, 24 Nov 2015 16:01:02 -0800 [thread overview]
Message-ID: <5654FA3E.6020609@gmail.com> (raw)
In-Reply-To: <1444905142-21500-4-git-send-email-l.stach@pengutronix.de>
On 15/10/15 03:32, Lucas Stach wrote:
> This is not needed anymore. Handling a potentially pending imprecise external
> abort left behind by the bootloader is now done in a slightly safer way inside
> the common ARM startup code.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
Applied to soc/next, thanks!
--
Florian
next prev parent reply other threads:[~2015-11-25 0:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 10:32 [PATCH v2 0/3] ARM: handle imprecise aborts from firmware in common code Lucas Stach
2015-10-15 10:32 ` [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask Lucas Stach
2015-10-15 15:32 ` Russell King - ARM Linux
2015-10-15 15:39 ` Tony Lindgren
2015-10-15 16:06 ` Russell King - ARM Linux
2015-10-15 16:23 ` Tony Lindgren
2015-10-16 8:21 ` Lucas Stach
2015-10-19 12:41 ` Lucas Stach
2015-10-15 10:32 ` [PATCH v2 2/3] ARM: OMAP2+: remove custom abort handler for t410 Lucas Stach
2015-11-12 13:32 ` Lucas Stach
2015-11-12 17:51 ` Tony Lindgren
2015-10-15 10:32 ` [PATCH v2 3/3] ARM: BCM5301X: remove workaround imprecise abort fault handler Lucas Stach
2015-11-25 0:01 ` Florian Fainelli [this message]
2015-10-16 19:11 ` [PATCH v2 0/3] ARM: handle imprecise aborts from firmware in common code Tyler Baker
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=5654FA3E.6020609@gmail.com \
--to=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patchwork-lst@pengutronix.de \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).