[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200905135714.74bsr5h423k7guw4@ltop.local>
Date: Sat, 5 Sep 2020 15:57:14 +0200
From: Luc Van Oostenryck <luc.vanoostenryck@...il.com>
To: Stafford Horne <shorne@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Jonas Bonn <jonas@...thpole.se>,
Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
Andrew Morton <akpm@...ux-foundation.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Greentime Hu <green.hu@...il.com>,
openrisc@...ts.librecores.org
Subject: Re: [PATCH v2 3/3] openrisc: Fix issue with get_user for 64-bit
values
On Sat, Sep 05, 2020 at 10:19:35PM +0900, Stafford Horne wrote:
Hi,
The change for 64-bit get_user() looks good to me.
But I wonder, given that openrisc is big-endian, what will happen
you have the opposite situation:
u32 *ptr;
u64 val;
...
get_user(val, ptr);
Won't you end with the value in the most significant part of
the register pair?
-- Luc
Powered by blists - more mailing lists