From: Tony Lindgren <tony@atomide.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Nishanth Menon" <nm@ti.com>,
"Ивайло Димитров" <freemangordon@abv.bg>,
linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround
Date: Wed, 27 Mar 2013 13:56:07 -0700 [thread overview]
Message-ID: <20130327205606.GN10155@atomide.com> (raw)
In-Reply-To: <201303241526.59275@pali>
* Pali Rohár <pali.rohar@gmail.com> [130324 07:31]:
> it is possible to upstream errata 430973 workaround for RX-51?
I think we should make the SMC handling a generic function for ARM.
AFAIK just the SMC call numbering is different for various
implementations. So the handler and passing of the parameters
seems like it should be generic.
Regards,
Tony
next prev parent reply other threads:[~2013-03-27 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 7:47 [PATCH] arm: omap: RX-51: ARM errata 430973 workaround Ивайло Димитров
2013-03-01 14:38 ` Nishanth Menon
2013-03-04 18:58 ` Tony Lindgren
2013-03-06 14:09 ` Pali Rohár
2013-03-06 17:51 ` Tony Lindgren
2013-03-06 19:13 ` Pali Rohár
2013-03-24 14:26 ` Pali Rohár
2013-03-27 20:56 ` Tony Lindgren [this message]
2013-03-27 21:05 ` Pali Rohár
2013-03-27 21:12 ` Tony Lindgren
2013-03-28 9:50 ` Russell King - ARM Linux
2013-03-28 10:07 ` Santosh Shilimkar
2013-03-28 15:53 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2013-03-30 22:31 Ивайло Димитров
2013-03-31 7:37 ` Pavel Machek
2013-03-28 5:30 Ивайло Димитров
2013-03-28 15:58 ` Tony Lindgren
2013-03-06 9:32 Ивайло Димитров
2013-03-01 10:09 Ивайло Димитров
2013-03-01 23:51 ` Aaro Koskinen
2013-02-28 9:42 Pali Rohár
2013-02-28 14:40 ` Nishanth Menon
2013-03-01 9:43 ` Peter De Schrijver
2013-03-30 18:36 ` Pavel Machek
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=20130327205606.GN10155@atomide.com \
--to=tony@atomide.com \
--cc=freemangordon@abv.bg \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.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).