[PATCH] scsi: ufs: core: Update contact email for monitor sysfs nodes

From: Can Guo
Date: Thu Jun 29 2023 - 01:29:43 EST


Update contact email address for UFS monitor sysfs nodes.

Signed-off-by: Can Guo <quic_cang@xxxxxxxxxxx>

diff --git a/Documentation/ABI/testing/sysfs-driver-ufs b/Documentation/ABI/testing/sysfs-driver-ufs
index d5f44fc5b9dc..86d2d63c18ba 100644
--- a/Documentation/ABI/testing/sysfs-driver-ufs
+++ b/Documentation/ABI/testing/sysfs-driver-ufs
@@ -1084,7 +1084,7 @@ Description: This entry shows the target state of an UFS UIC link
What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_enable
What: /sys/bus/platform/devices/*.ufs/monitor/monitor_enable
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the status of performance monitor enablement
and it can be used to start/stop the monitor. When the monitor
is stopped, the performance data collected is also cleared.
@@ -1092,7 +1092,7 @@ Description: This file shows the status of performance monitor enablement
What: /sys/bus/platform/drivers/ufshcd/*/monitor/monitor_chunk_size
What: /sys/bus/platform/devices/*.ufs/monitor/monitor_chunk_size
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file tells the monitor to focus on requests transferring
data of specific chunk size (in Bytes). 0 means any chunk size.
It can only be changed when monitor is disabled.
@@ -1100,7 +1100,7 @@ Description: This file tells the monitor to focus on requests transferring
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_sectors
What: /sys/bus/platform/devices/*.ufs/monitor/read_total_sectors
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how many sectors (in 512 Bytes) have been
sent from device to host after monitor gets started.

@@ -1109,7 +1109,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_total_busy
What: /sys/bus/platform/devices/*.ufs/monitor/read_total_busy
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how long (in micro seconds) has been spent
sending data from device to host after monitor gets started.

@@ -1118,7 +1118,7 @@ Description: This file shows how long (in micro seconds) has been spent
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_nr_requests
What: /sys/bus/platform/devices/*.ufs/monitor/read_nr_requests
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how many read requests have been sent after
monitor gets started.

@@ -1127,7 +1127,7 @@ Description: This file shows how many read requests have been sent after
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_max
What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_max
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the maximum latency (in micro seconds) of
read requests after monitor gets started.

@@ -1136,7 +1136,7 @@ Description: This file shows the maximum latency (in micro seconds) of
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_min
What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_min
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the minimum latency (in micro seconds) of
read requests after monitor gets started.

@@ -1145,7 +1145,7 @@ Description: This file shows the minimum latency (in micro seconds) of
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_avg
What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_avg
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the average latency (in micro seconds) of
read requests after monitor gets started.

@@ -1154,7 +1154,7 @@ Description: This file shows the average latency (in micro seconds) of
What: /sys/bus/platform/drivers/ufshcd/*/monitor/read_req_latency_sum
What: /sys/bus/platform/devices/*.ufs/monitor/read_req_latency_sum
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the total latency (in micro seconds) of
read requests sent after monitor gets started.

@@ -1163,7 +1163,7 @@ Description: This file shows the total latency (in micro seconds) of
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_sectors
What: /sys/bus/platform/devices/*.ufs/monitor/write_total_sectors
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how many sectors (in 512 Bytes) have been sent
from host to device after monitor gets started.

@@ -1172,7 +1172,7 @@ Description: This file shows how many sectors (in 512 Bytes) have been sent
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_total_busy
What: /sys/bus/platform/devices/*.ufs/monitor/write_total_busy
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how long (in micro seconds) has been spent
sending data from host to device after monitor gets started.

@@ -1181,7 +1181,7 @@ Description: This file shows how long (in micro seconds) has been spent
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_nr_requests
What: /sys/bus/platform/devices/*.ufs/monitor/write_nr_requests
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows how many write requests have been sent after
monitor gets started.

@@ -1190,7 +1190,7 @@ Description: This file shows how many write requests have been sent after
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_max
What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_max
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the maximum latency (in micro seconds) of write
requests after monitor gets started.

@@ -1199,7 +1199,7 @@ Description: This file shows the maximum latency (in micro seconds) of write
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_min
What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_min
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the minimum latency (in micro seconds) of write
requests after monitor gets started.

@@ -1208,7 +1208,7 @@ Description: This file shows the minimum latency (in micro seconds) of write
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_avg
What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_avg
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the average latency (in micro seconds) of write
requests after monitor gets started.

@@ -1217,7 +1217,7 @@ Description: This file shows the average latency (in micro seconds) of write
What: /sys/bus/platform/drivers/ufshcd/*/monitor/write_req_latency_sum
What: /sys/bus/platform/devices/*.ufs/monitor/write_req_latency_sum
Date: January 2021
-Contact: Can Guo <cang@xxxxxxxxxxxxxx>
+Contact: Can Guo <quic_cang@xxxxxxxxxxx>
Description: This file shows the total latency (in micro seconds) of write
requests after monitor gets started.

--
2.25.1