linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "James E . J . Bottomley" <jejb@linux.ibm.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>, Can Guo <cang@codeaurora.org>,
	Stanley Chu <stanley.chu@mediatek.com>
Subject: Re: [PATCH V2] scsi: ufs-pci: Add LTR support for Intel controllers
Date: Fri, 11 Sep 2020 17:01:08 +0300	[thread overview]
Message-ID: <841d40b4-1181-2bd3-2c7f-4c00e76cbe60@intel.com> (raw)
In-Reply-To: <a27fa387-356c-82e1-a49f-62602336589e@intel.com>

On 9/09/20 5:06 pm, Adrian Hunter wrote:
> On 2/09/20 12:27 pm, Adrian Hunter wrote:
>> On 2/09/20 5:12 am, Martin K. Petersen wrote:
>>>
>>> Adrian,
>>>
>>>> Intel host controllers support the setting of latency tolerance.
>>>> Accordingly, implement the PM QoS ->set_latency_tolerance() callback. The
>>>> raw register values are also exposed via debugfs.
>>>
>>> Does not apply to 5.10/scsi-queue. Please rebase. Thanks!
>>>
>>
>> Hi
>>
>> Thanks for processing this.
>>
>> The 5.10/scsi-queue branch seems to be missing the following fix.  If you cherry
>> pick that, then it applies.
> 
> Now there seem to be conflicts between 5.10/scsi-queue and v5.9-rc4.
> I am not sure what I can do?

Now I see it does apply to James' for-next branch.  Can it be applied there?

  reply	other threads:[~2020-09-11 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27  7:20 [PATCH V2] scsi: ufs-pci: Add LTR support for Intel controllers Adrian Hunter
2020-08-27 12:08 ` Avri Altman
2020-09-02  2:12 ` Martin K. Petersen
2020-09-02  9:27   ` Adrian Hunter
2020-09-09 14:06     ` Adrian Hunter
2020-09-11 14:01       ` Adrian Hunter [this message]
2020-09-11 14:28         ` Martin K. Petersen
2020-09-15 20:19 ` Martin K. Petersen
2020-09-22  3:56 ` 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=841d40b4-1181-2bd3-2c7f-4c00e76cbe60@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=cang@codeaurora.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stanley.chu@mediatek.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;
as well as URLs for NNTP newsgroup(s).