[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210421120055.GA8637@alpha.franken.de>
Date: Wed, 21 Apr 2021 14:00:55 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: xiaochuan mao <maoxiaochuan@...ngson.cn>
Cc: 周琰杰 <zhouyanjie@...yeetech.com>,
Paul Cercueil <paul@...pouillou.net>,
Florian Fainelli <f.fainelli@...il.com>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
michael <michael5hzg@...il.com>
Subject: Re: [PATCH] mips/bootinfo:correct some comments of fw_arg
On Wed, Apr 21, 2021 at 02:19:17PM +0800, xiaochuan mao wrote:
> from arch/mips/kernel/head.S we know that use a0~a3 for fw_arg0~fw_arg3
> there is some code from head.S:
> LONG_S a0, fw_arg0 # firmware arguments
> LONG_S a1, fw_arg1
> LONG_S a2, fw_arg2
> LONG_S a3, fw_arg3
>
> Signed-off-by: xiaochuan mao <maoxiaochuan@...ngson.cn>
> ---
> arch/mips/include/asm/bootinfo.h | 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