[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210412150704.GD23632@alpha.franken.de>
Date: Mon, 12 Apr 2021 17:07:04 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Chen Lifu <chenlifu@...wei.com>
Cc: Zhang Qilong <zhangqilong3@...wei.com>, heying24@...wei.com,
yuehaibing@...wei.com, weiyongjun1@...wei.com,
johnny.chenyi@...wei.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH -next] MIPS: Alchemy: Use DEFINE_SPINLOCK() for spinlock
On Sat, Mar 27, 2021 at 05:52:25PM +0800, Chen Lifu wrote:
> From: Lifu Chen <chenlifu@...wei.com>
>
> spinlock can be initialized automatically with DEFINE_SPINLOCK()
> rather than explicitly calling spin_lock_init().
>
> Reported-by: Hulk Robot <hulkci@...wei.com>
> Signed-off-by: Lifu Chen <chenlifu@...wei.com>
> ---
> arch/mips/alchemy/common/clock.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
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