public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keoseong Park <keosung.park@samsung.com>
To: Avri Altman <Avri.Altman@sandisk.com>,
	Keoseong Park <keosung.park@samsung.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	Daejun Park <daejun7.park@samsung.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Bao D . Nguyen" <quic_nguyenb@quicinc.com>
Subject: RE:(2) [PATCH] scsi: ufs: Fix incorrect bit assignment for temperature notifications
Date: Mon, 17 Feb 2025 11:39:00 +0900	[thread overview]
Message-ID: <1891546521.01739765283208.JavaMail.epsvc@epcpadp2new> (raw)
In-Reply-To: <PH7PR16MB61965AFF2D91331975BBD24EE5FE2@PH7PR16MB6196.namprd16.prod.outlook.com>

> + Bao
>
>> According to the UFS specification, the bit positions for
>> `UFS_DEV_HIGH_TEMP_NOTIF` and `UFS_DEV_LOW_TEMP_NOTIF` were
>> incorrectly assigned. This patch corrects the bit assignment to align with the
>> specification.
>> 
>> If this issue is not fixed, devices that support both high and low temperature
>> notifications may function correctly, but devices that support only one of
>> them may fail to trigger the corresponding exception event.
>> 
>> Fixes: e88e2d32200a ("scsi: ufs: core: Probe for temperature notification
>> support")
>> Signed-off-by: Keoseong Park <keosung.park@samsung.com>
> Already noticed by Bao D. Nguyen - see https://protect2.fireeye.com/v1/url?k=81dbf2a5-e050e79f-81da79ea-74fe4860008a-0424961c73a03c70&q=1&e=fcfc99c7-cb2b-4f68-8ef4-e2760c685fec&u=https%3A%2F%2Fwww.spinics.net%2Flists%2Flinux-scsi%2Fmsg202162.html
>
> Thanks,
> Avri
>

Hi Avri,

Thank you for the update. I wasn’t aware that Bao D. Nguyen’s patch had already been applied.  
I appreciate the heads-up, and I’ll make sure to check the latest patches more carefully next time.  

Best Regards,
Keoseong

>> ---
>>  include/ufs/ufs.h | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/include/ufs/ufs.h b/include/ufs/ufs.h index
>> d335bff1a310..8a24ed59ec46 100644
>> --- a/include/ufs/ufs.h
>> +++ b/include/ufs/ufs.h
>> @@ -385,8 +385,8 @@ enum {
>> 
>>  /* Possible values for dExtendedUFSFeaturesSupport */  enum {
>> -	UFS_DEV_LOW_TEMP_NOTIF		= BIT(4),
>> -	UFS_DEV_HIGH_TEMP_NOTIF		= BIT(5),
>> +	UFS_DEV_HIGH_TEMP_NOTIF		= BIT(4),
>> +	UFS_DEV_LOW_TEMP_NOTIF		= BIT(5),
>>  	UFS_DEV_EXT_TEMP_NOTIF		= BIT(6),
>>  	UFS_DEV_HPB_SUPPORT		= BIT(7),
>>  	UFS_DEV_WRITE_BOOSTER_SUP	= BIT(8),
>> --
>> 2.25.1
>> 
>> 
>

      reply	other threads:[~2025-02-17  4:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250214105219epcms2p3a60810a14e6181092cb397924ce36019@epcms2p3>
2025-02-14 10:52 ` [PATCH] scsi: ufs: Fix incorrect bit assignment for temperature notifications Keoseong Park
2025-02-14 17:46   ` Avri Altman
2025-02-17  2:39     ` Keoseong Park [this message]

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=1891546521.01739765283208.JavaMail.epsvc@epcpadp2new \
    --to=keosung.park@samsung.com \
    --cc=Avri.Altman@sandisk.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=daejun7.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=martin.petersen@oracle.com \
    --cc=quic_nguyenb@quicinc.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