From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: SEO HOYOUNG <hy50.seo@samsung.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
bvanassche@acm.org, kwangwon.min@samsung.com,
kwmad.kim@samsung.com, sh425.lee@samsung.com,
quic_nguyenb@quicinc.com, cpgs@samsung.com, h10.kim@samsung.com,
grant.jung@samsung.com, junwoo80.lee@samsung.com,
wkon.kim@samsung.com
Subject: Re: [PATCH v3 1/2] scsi: ufs: core: check asymmetric connected lanes
Date: Fri, 25 Oct 2024 14:37:53 -0400 [thread overview]
Message-ID: <yq1r084f2q1.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <e82b4b65b5f6501a687c624dd06e5c362e160f32.1728544727.git.hy50.seo@samsung.com> (SEO HOYOUNG's message of "Thu, 10 Oct 2024 16:52:28 +0900")
> Performance problems may occur if there is a problem with the
> asymmetric connected lane such as h/w failure. Currently, only check
> connected lane for rx/tx is checked if it is not 0. But it should also
> be checked if it is asymmetrically connected.
Applied to 6.13/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-10-25 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241010074222epcas2p4278413120c00584d83f654dbde6c0f49@epcas2p4.samsung.com>
2024-10-10 7:52 ` [PATCH v3 0/2] processing of asymmetric connected lanes SEO HOYOUNG
2024-10-10 7:52 ` [PATCH v3 1/2] scsi: ufs: core: check " SEO HOYOUNG
2024-10-15 18:16 ` Bart Van Assche
2024-10-25 18:37 ` Martin K. Petersen [this message]
2024-10-10 7:52 ` [PATCH v3 2/2] scsi: ufs: core: reflect function execution result in return SEO HOYOUNG
2024-10-15 18:13 ` Bart Van Assche
2024-11-05 2:32 ` [PATCH v3 0/2] processing of asymmetric connected lanes Martin K. Petersen
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=yq1r084f2q1.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cpgs@samsung.com \
--cc=grant.jung@samsung.com \
--cc=h10.kim@samsung.com \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=junwoo80.lee@samsung.com \
--cc=kwangwon.min@samsung.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=quic_nguyenb@quicinc.com \
--cc=sh425.lee@samsung.com \
--cc=wkon.kim@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox