public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Alim Akhtar <alim.akhtar@samsung.com>,
	'Hoyoung SEO' <hy50.seo@samsung.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	avri.altman@wdc.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, beanhuo@micron.com,
	asutoshd@codeaurora.org, cang@codeaurora.org,
	bhoon95.kim@samsung.com, kwmad.kim@samsung.com
Cc: 'kernel test robot' <lkp@intel.com>
Subject: Re: [PATCH v2] scsi: ufs: disable auto hibern8 while entering suspend
Date: Thu, 3 Feb 2022 08:53:40 -0800	[thread overview]
Message-ID: <54be0878-a7da-cc8a-3efc-1bb0c53caf47@acm.org> (raw)
In-Reply-To: <066101d818ca$5dba71f0$192f55d0$@samsung.com>

On 2/2/22 22:50, Alim Akhtar wrote:
> I am not sure, if this problem is generic and faced by all other UFS vendors.
> If not, how about having a vendor specific call back for your platform only?
> Just a thought.

I agree with the above. Since the code change does not follow from the 
spec, it should be guarded with a check for a new quirk flag.

Thanks,

Bart.

      reply	other threads:[~2022-02-03 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220125062155epcas2p15da28303164091b1bf5a00dcf99fe59b@epcas2p1.samsung.com>
2022-01-24 18:06 ` [PATCH v2] scsi: ufs: disable auto hibern8 while entering suspend SEO HOYOUNG
2022-01-26  1:22   ` Stanley Chu
2022-01-26  5:34     ` 서호영
2022-02-03  0:12     ` Hoyoung SEO
2022-02-03  6:44       ` Avri Altman
2022-02-03  6:50       ` Alim Akhtar
2022-02-03 16:53         ` Bart Van Assche [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=54be0878-a7da-cc8a-3efc-1bb0c53caf47@acm.org \
    --to=bvanassche@acm.org \
    --cc=alim.akhtar@samsung.com \
    --cc=asutoshd@codeaurora.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bhoon95.kim@samsung.com \
    --cc=cang@codeaurora.org \
    --cc=hy50.seo@samsung.com \
    --cc=jejb@linux.ibm.com \
    --cc=kwmad.kim@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=martin.petersen@oracle.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