All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chen Lifu <chenlifu@huawei.com>
Cc: Zhang Qilong <zhangqilong3@huawei.com>,
	heying24@huawei.com, yuehaibing@huawei.com,
	weiyongjun1@huawei.com, johnny.chenyi@huawei.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] MIPS: Alchemy: Use DEFINE_SPINLOCK() for spinlock
Date: Mon, 12 Apr 2021 17:07:04 +0200	[thread overview]
Message-ID: <20210412150704.GD23632@alpha.franken.de> (raw)
In-Reply-To: <20210327095225.104997-1-chenlifu@huawei.com>

On Sat, Mar 27, 2021 at 05:52:25PM +0800, Chen Lifu wrote:
> From: Lifu Chen <chenlifu@huawei.com>
> 
> spinlock can be initialized automatically with DEFINE_SPINLOCK()
> rather than explicitly calling spin_lock_init().
> 
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Lifu Chen <chenlifu@huawei.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 ]

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Chen Lifu <chenlifu@huawei.com>
Cc: Zhang Qilong <zhangqilong3@huawei.com>,
	heying24@huawei.com, yuehaibing@huawei.com,
	weiyongjun1@huawei.com, johnny.chenyi@huawei.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] MIPS: Alchemy: Use DEFINE_SPINLOCK() for spinlock
Date: Mon, 12 Apr 2021 17:07:04 +0200	[thread overview]
Message-ID: <20210412150704.GD23632@alpha.franken.de> (raw)
In-Reply-To: <20210327095225.104997-1-chenlifu@huawei.com>

On Sat, Mar 27, 2021 at 05:52:25PM +0800, Chen Lifu wrote:
> From: Lifu Chen <chenlifu@huawei.com>
> 
> spinlock can be initialized automatically with DEFINE_SPINLOCK()
> rather than explicitly calling spin_lock_init().
> 
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Lifu Chen <chenlifu@huawei.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 ]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-04-12 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  9:52 [PATCH -next] MIPS: Alchemy: Use DEFINE_SPINLOCK() for spinlock Chen Lifu
2021-03-27  9:52 ` Chen Lifu
2021-04-12 15:07 ` Thomas Bogendoerfer [this message]
2021-04-12 15:07   ` Thomas Bogendoerfer

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=20210412150704.GD23632@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=chenlifu@huawei.com \
    --cc=heying24@huawei.com \
    --cc=johnny.chenyi@huawei.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=weiyongjun1@huawei.com \
    --cc=yuehaibing@huawei.com \
    --cc=zhangqilong3@huawei.com \
    /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.