Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp98942yba; Mon, 20 May 2019 05:41:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqwPXxJ83N5XKbbWslsyXiSFSf3b9vx7NKt8urjPOSQXOJuqdTu5bLBgsRmrZJ/O3eV47LsT X-Received: by 2002:a17:902:c85:: with SMTP id 5mr1499002plt.172.1558356073316; Mon, 20 May 2019 05:41:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558356073; cv=none; d=google.com; s=arc-20160816; b=QfpWd79If4BePjIzHUBOny9iVzbJHOrOWoaNcwtE+IzZzQgkPRyDJbIaj8naI7yq/r CdPO5WrROfdBkV9C9STdIM192KGrJ3h4UlEJEgb4YVcsk2JbBLLaSxQX3UQLrzZKgAnv Eyee9WwFr7JHgAGhb42fX5VoLGdJe2uyf9u2Kq5IlJhIN0q8w7x7a4AArjhpCC1L83MK 6MD3R/0DJ/Wk7AMSTQbgF9UAubr+iY42KsjnnmaPF6FNE7Vfc/YeC4cijqzeuquXuimi 2O5mnqTaO+lDtfmlhZdD9t0f9UIb3NeU8x+NPY1rVxx79iDD4aRq5BXXEweqdqe83eY5 WDSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=bKoF+je4tztiMZeVL4QdGxF6fmfoZKMQsYY23DhoQmU=; b=HQtORtc0FjnWEs1KuWASiJgAC0Yecwa5Vq8m4X24VD6cmlvJQjYe1Po0qE95ZN7h50 g/POJf2waVc/0Esl0QippHFPPa0vaTH1HJacqj0yeDIz1F0F2N3zQeJpFBycPlp+q/Ou jhpcNIjszcWWq6n8Zf9EUjnWsJLwErtC3oy+5xexPda4Wvj3LxONVRnnDT1NDk4K4EPG 6L76A8i49FCq9ApuDCuvDK9juDBALkyyOdVA22p1KmSozgvo8qB38ddYTyRJSyfhrH6m spzkuaicyNz1URTLn2SPBU21VJU2HPLbztNw7AQ+c0G7Fu7h58V9SJZ2KtUhDPCAFkqy m/Ag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c2si9316497pgq.254.2019.05.20.05.40.58; Mon, 20 May 2019 05:41:13 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391356AbfETMjW (ORCPT + 99 others); Mon, 20 May 2019 08:39:22 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:7663 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2391027AbfETMjU (ORCPT ); Mon, 20 May 2019 08:39:20 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id BD55920955D48F696694; Mon, 20 May 2019 20:39:17 +0800 (CST) Received: from [127.0.0.1] (10.202.227.238) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.439.0; Mon, 20 May 2019 20:39:09 +0800 Subject: Re: [PATCH] scsi: libsas: no need to join wide port again in sas_ex_discover_dev() To: Jason Yan , , References: <20190518094057.18046-1-yanaijie@huawei.com> <1860c624-1216-bb84-7091-d41a4d43f244@huawei.com> <61b6d28d-7b5f-f078-c035-77e855fbe8bf@huawei.com> CC: , , , , , , , , , From: John Garry Message-ID: <83a50fae-78f4-d236-a007-7e8d95553415@huawei.com> Date: Mon, 20 May 2019 13:39:00 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <61b6d28d-7b5f-f078-c035-77e855fbe8bf@huawei.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.227.238] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/05/2019 13:06, Jason Yan wrote: > OK. > >> >> In case of "second fanout expander...", before this, we don't attempt >> to discover, and just disable the PHY. In that case, is the log proper? >> > > In that case the log is not proper. I think we can directly return in > the case of "second fanout expander..."? Actually nothing to do after > the phy is disabled. Yeah, that looks fine. > >> And, if indeed proper, it would seem to merit a higher log level than >> debug, maybe notice is better.