From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ARM: vfp: Fix VFPv3 hwcap detection on CPUID based cpus
Date: Tue, 28 Oct 2014 10:54:59 -0700 [thread overview]
Message-ID: <20141028175459.GE12469@codeaurora.org> (raw)
In-Reply-To: <20141028121154.GA12136@arm.com>
On 10/28, Will Deacon wrote:
>
> Sure. There's a spelling mistake ("arhitecture") which you should fix,
> but the code looks ok.
Ok I'll fix it up and send it off to the patch tracker if I don't
hear anything else.
> >
> > I have an RFC for the undef handler written up, except for the
> > big/little thing. Let me post it. Is there anyone from the userspace
> > side that can be on Cc?
>
> Off the top of my head:
>
> Mans Rullgard (already replied to this thread)
> Peter Maydell <peter.maydell@linaro.org> [QEMU]
> Jacob Bramley <jacob.bramley@arm.com> [JITs]
> Kyrylo Tkachov <kyrylo.tkachov@arm.com> [GCC]
>
Thanks. I'll add them to the patch for next round and add them on
Cc for the current patch on the list.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-28 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 13:48 [PATCH v2 0/3] VFP fixes Stephen Boyd
2014-10-14 13:48 ` [PATCH v2 1/3] ARM: vfp: Workaround bad MVFR1 register on some Kraits Stephen Boyd
2014-10-14 13:48 ` [PATCH v2 2/3] ARM: vfp: Fix VFPv3 hwcap detection on CPUID based cpus Stephen Boyd
2014-10-27 10:31 ` Will Deacon
2014-10-27 11:49 ` Måns Rullgård
2014-10-27 19:50 ` Stephen Boyd
2014-10-28 12:11 ` Will Deacon
2014-10-28 17:54 ` Stephen Boyd [this message]
2014-10-14 13:48 ` [PATCH v2 3/3] arm: vfp: Bounce undefined instructions in vectored mode Stephen Boyd
2014-10-16 13:14 ` [PATCH v2 0/3] VFP fixes Rob Clark
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=20141028175459.GE12469@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).