[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200716095213.GD8455@alpha.franken.de>
Date: Thu, 16 Jul 2020 11:52:14 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Guoyun Sun <sunguoyun@...ngson.cn>
Cc: Paul Burton <paulburton@...nel.org>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, Tiezhu Yang <yangtiezhu@...ngson.cn>
Subject: Re: [PATCH] MIPS: fix vdso different address spaces
On Tue, Jul 14, 2020 at 02:07:47PM +0800, Guoyun Sun wrote:
> From: Sunguoyun <sunguoyun@...ngson.cn>
>
> sparse report build warning as follows:
> arch/mips/vdso/vdso-n32-image.c:13:35:
> incorrect type in assignment (different address spaces) @@
> expected void *[usertype] vdso @@ got void [noderef] <asn:1> * @@
>
> Reported-by: kernel test robot <lkp@...el.com>
>
> Signed-off-by: Sunguoyun <sunguoyun@...ngson.cn>
> ---
> arch/mips/vdso/genvdso.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists