From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: accessing vfpinstr macros from outside vfp directory
Date: Fri, 01 Apr 2011 18:27:23 +0100 [thread overview]
Message-ID: <1301678843.17592.5.camel@e102144-lin.cambridge.arm.com> (raw)
In-Reply-To: <4D924966.2050707@codeaurora.org>
Neil,
On Tue, 2011-03-29 at 22:04 +0100, Neil Leeder wrote:
> Any opinions on what would be the best thing to do here? Choices appear to be:
>
> 1) allow the relative include path of ../vfp/vfpinstr.h
> 2) move the definitions of fmrx, fmxr from vfp/vfpinstr.h to include/asm/vfp.h
> 3) move vfp/vfpinstr.h to include/asm
> 4) other...?
>
> If it helps, I can create a patch for whichever is considered the preferred solution.
>
I personally don't find option (1) that offensive - Bryan seemed to
differ though so perhaps option (2) would keep him happy?
I don't think option (3) is sensible given that the majority of the
header file is private to /vfp.
Will
next prev parent reply other threads:[~2011-04-01 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 21:04 accessing vfpinstr macros from outside vfp directory Neil Leeder
2011-04-01 17:27 ` Will Deacon [this message]
2011-04-01 21:54 ` Bryan Huntsman
2011-04-03 12:24 ` Will Deacon
2011-04-04 14:16 ` Neil Leeder
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=1301678843.17592.5.camel@e102144-lin.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).