All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangyijing <wangyijing@huawei.com>
To: John Garry <john.garry@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	<chenqilin2@huawei.com>, <hare@suse.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<chenxiang66@hisilicon.com>, <huangdaode@hisilicon.com>,
	<wangkefeng.wang@huawei.com>, <zhaohongjiang@huawei.com>,
	<dingtianhong@huawei.com>, <guohanjun@huawei.com>,
	Wei Fang <fangwei1@huawei.com>, <yanaijie@huawei.com>,
	Christoph Hellwig <hch@lst.de>, Yousong He <heyousong@huawei.com>,
	Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH 1/2] libsas: Don't process sas events in static works
Date: Tue, 23 May 2017 14:39:21 +0800	[thread overview]
Message-ID: <5923D919.30408@huawei.com> (raw)
In-Reply-To: <392354c0-a4a1-99a8-7723-25513efb835c@huawei.com>

>>
> 
> I have seen this scenario on our development board when we have a bad physical cable connection - the PHY continually goes up and down in a loop.
> 
> So, in this regard, it is worth safeguarding against this scenario.

OK, I will reconsider this case.

Thanks!
Yijing.


> 
> John
> 
> 
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: wangyijing <wangyijing@huawei.com>
To: John Garry <john.garry@huawei.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	chenqilin2@huawei.com, hare@suse.com,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	chenxiang66@hisilicon.com, huangdaode@hisilicon.com,
	wangkefeng.wang@huawei.com, zhaohongjiang@huawei.com,
	dingtianhong@huawei.com, guohanjun@huawei.com,
	Wei Fang <fangwei1@huawei.com>,
	yanaijie@huawei.com, Christoph Hellwig <hch@lst.de>,
	Yousong He <heyousong@huawei.com>, Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH 1/2] libsas: Don't process sas events in static works
Date: Tue, 23 May 2017 14:39:21 +0800	[thread overview]
Message-ID: <5923D919.30408@huawei.com> (raw)
In-Reply-To: <392354c0-a4a1-99a8-7723-25513efb835c@huawei.com>

>>
> 
> I have seen this scenario on our development board when we have a bad physical cable connection - the PHY continually goes up and down in a loop.
> 
> So, in this regard, it is worth safeguarding against this scenario.

OK, I will reconsider this case.

Thanks!
Yijing.


> 
> John
> 
> 
> .
> 

  reply	other threads:[~2017-05-23  6:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20  6:39 [PATCH 0/2] Enhance libsas hotplug feature Yijing Wang
2017-05-20  6:39 ` Yijing Wang
2017-05-20  6:39 ` [PATCH 1/2] libsas: Don't process sas events in static works Yijing Wang
2017-05-20  6:39   ` Yijing Wang
2017-05-21  3:44   ` Dan Williams
2017-05-22  5:54     ` wangyijing
2017-05-22  5:54       ` wangyijing
2017-05-22  9:28       ` John Garry
2017-05-22  9:28         ` John Garry
2017-05-23  6:39         ` wangyijing [this message]
2017-05-23  6:39           ` wangyijing
2017-05-20  6:39 ` [PATCH 2/2] libsas: Enhance libsas hotplug Yijing Wang
2017-05-20  6:39   ` Yijing Wang
2017-05-25  9:04   ` John Garry
2017-05-25  9:04     ` John Garry
2017-05-25 12:31     ` wangyijing
2017-05-25 12:31       ` wangyijing

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=5923D919.30408@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=chenqilin2@huawei.com \
    --cc=chenxiang66@hisilicon.com \
    --cc=dan.j.williams@intel.com \
    --cc=dingtianhong@huawei.com \
    --cc=fangwei1@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=heyousong@huawei.com \
    --cc=huangdaode@hisilicon.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=yanaijie@huawei.com \
    --cc=zhaohongjiang@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.