Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] scsi: bnx2fc: Make use of the helper macro kthread_run()
To:     Cai Huoqing <caihuoqing@baidu.com>
CC:     Saurav Kashyap <skashyap@marvell.com>,
        Javed Hasan <jhasan@marvell.com>,
        <GR-QLogic-Storage-Upstream@marvell.com>,
        "James E.J. Bottomley" <jejb@linux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@oracle.com>,
        <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
References: <20211021084221.2342-1-caihuoqing@baidu.com>
From:   John Garry <john.garry@huawei.com>
Message-ID: <834fa2cc-8a4a-b632-93bb-43d2dfdc4713@huawei.com>
Date:   Fri, 22 Oct 2021 11:49:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <20211021084221.2342-1-caihuoqing@baidu.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 21/10/2021 09:42, Cai Huoqing wrote:
> Repalce kthread_create/wake_up_process() with kthread_run()

Replace

> to simplify the code.
> 
> Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
> ---
>   drivers/scsi/bnx2fc/bnx2fc_fcoe.c | 5 ++---
>   1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> index 71fa62bd3083..975512511a60 100644
> --- a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> +++ b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> @@ -2723,9 +2723,8 @@ static int __init bnx2fc_mod_init(void)
>   
>   	bg = &bnx2fc_global;
>   	skb_queue_head_init(&bg->fcoe_rx_list);
> -	l2_thread = kthread_create(bnx2fc_l2_rcv_thread,
> -				   (void *)bg,
> -				   "bnx2fc_l2_thread");
> +	l2_thread = kthread_run(bnx2fc_l2_rcv_thread,
> +				(void *)bg, "bnx2fc_l2_thread");
>   	if (IS_ERR(l2_thread)) {
>   		rc = PTR_ERR(l2_thread);
>   		goto free_wq;

Are you then supposed to remove the wake_up_process() call also (not shown)?

>