From: Chris Zankel <chris@zankel.net>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Bob Wilson <bwilson@tensilica.com>
Subject: Re: [PATCH 3/4] xtensa: Change unaligned access to use packed struct implementation
Date: Thu, 09 Oct 2008 22:16:54 -0700 [thread overview]
Message-ID: <48EEE546.9070405@zankel.net> (raw)
In-Reply-To: <1223447904.8195.67.camel@brick>
Hi Harvey,
Please allow me a couple of days to look into it. I don't know the
historic reasons why the memmove variant was chosen.
Thanks,
-Chris
Harvey Harrison wrote:
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> There are only 3 arches that use the memmove-based implementation, there
> doesn't seem to be any obvious reason not to use the struct implementation.
>
> Chris?
>
> include/asm-xtensa/unaligned.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-xtensa/unaligned.h b/include/asm-xtensa/unaligned.h
> index 8f3424f..1a242b2 100644
> --- a/include/asm-xtensa/unaligned.h
> +++ b/include/asm-xtensa/unaligned.h
> @@ -11,13 +11,13 @@
> #define _ASM_XTENSA_UNALIGNED_H
>
> #ifdef __XTENSA_EL__
> -# include <linux/unaligned/le_memmove.h>
> +# include <linux/unaligned/le_struct.h>
> # include <linux/unaligned/be_byteshift.h>
> # include <linux/unaligned/generic.h>
> # define get_unaligned __get_unaligned_le
> # define put_unaligned __put_unaligned_le
> #elif defined(__XTENSA_EB__)
> -# include <linux/unaligned/be_memmove.h>
> +# include <linux/unaligned/be_struct.h>
> # include <linux/unaligned/le_byteshift.h>
> # include <linux/unaligned/generic.h>
> # define get_unaligned __get_unaligned_be
next prev parent reply other threads:[~2008-10-10 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 6:38 [PATCH 3/4] xtensa: Change unaligned access to use packed struct implementation Harvey Harrison
2008-10-10 5:16 ` Chris Zankel [this message]
2008-10-10 5:39 ` Harvey Harrison
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=48EEE546.9070405@zankel.net \
--to=chris@zankel.net \
--cc=akpm@linux-foundation.org \
--cc=bwilson@tensilica.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.