linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: alignment handler instruction endian-ness
Date: Mon, 22 Jul 2013 19:34:10 +0100	[thread overview]
Message-ID: <51ED7B22.9040104@codethink.co.uk> (raw)
In-Reply-To: <alpine.LFD.2.03.1307221428050.15022@syhkavp.arg>

On 22/07/13 19:31, Nicolas Pitre wrote:
> On Fri, 19 Jul 2013, Ben Dooks wrote:
>> On 19/07/13 13:32, Russell King - ARM Linux wrote:
>>> If you value your soul, NEVER EVER EVER place stuff which is not part
>>> of the user API in a header file in a UAPI subdirectory.  And never
>>> modify a header file in a UAPI subdirectory without first having a
>>> good long think about how that modification may impact _userspace_.
>>
>> Sorry, searched for byteorder.h and just did not notice.
>>
>> Where is the best place for these to go?
>
> You should really have a look at arch/arm/include/asm/opcodes.h.

Yes, re-worked using <asm/opcodes.h> thanks.

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  reply	other threads:[~2013-07-22 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 10:58 alignment handler instruction endian-ness Ben Dooks
2013-07-19 11:09 ` Russell King - ARM Linux
2013-07-19 11:26   ` Ben Dooks
2013-07-19 12:15   ` Ben Dooks
2013-07-19 12:32     ` Russell King - ARM Linux
2013-07-19 13:19       ` Ben Dooks
2013-07-22 18:31         ` Nicolas Pitre
2013-07-22 18:34           ` Ben Dooks [this message]
2013-07-19 14:01   ` Jon Medhurst (Tixy)
2013-07-19 14:05     ` Russell King - ARM Linux
2013-07-19 14:50       ` Ben Dooks
2013-07-19 14:56         ` Russell King - ARM Linux

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=51ED7B22.9040104@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --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).