From: Hans de Goede <hdegoede@redhat.com>
To: Tejun Heo <tj@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: rjw@rjwysocki.net, alan.cox@intel.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ata: libahci: devslp fixes
Date: Mon, 30 Jul 2018 17:26:45 +0200 [thread overview]
Message-ID: <bf4b860c-6f82-4a3f-8b81-5f5c93f4389e@redhat.com> (raw)
In-Reply-To: <20180730152256.GF1206094@devbig004.ftw2.facebook.com>
Hi,
On 30-07-18 17:22, Tejun Heo wrote:
> On Mon, Jul 30, 2018 at 08:15:47AM -0700, Srinivas Pandruvada wrote:
>> Hi Tejan,
>>
>> On Mon, 2018-07-02 at 12:01 -0700, Srinivas Pandruvada wrote:
>>> Some minor fixes to be able to correctly set devslp register
>>> to optimize power.
>>>
>>> Srinivas Pandruvada (2):
>>> ata: libahci: Correct setting of DEVSLP register
>>> ata: libahci: Allow reconfigure of DEVSLP register
>>>
>> Are you applying this series?
>
> I was waiting for Hans's reviews. Hans, what do you think?
Ah I missed that this was another series. With the caveat that
I do not really know that much about devslp, both patches
seem sensible to me, so both are:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Regards,
Hans
next prev parent reply other threads:[~2018-07-30 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 19:01 [PATCH 0/2] ata: libahci: devslp fixes Srinivas Pandruvada
2018-07-02 19:01 ` [PATCH 1/2] ata: libahci: Correct setting of DEVSLP register Srinivas Pandruvada
[not found] ` <CAAtuYK9zXJHhJ8_aRqfqOPJJ9L29patDA9RuUs9r+GJVZMCy=Q@mail.gmail.com>
2018-07-17 3:43 ` Srinivas Pandruvada
2018-07-02 19:01 ` [PATCH 2/2] ata: libahci: Allow reconfigure " Srinivas Pandruvada
2018-07-30 15:15 ` [PATCH 0/2] ata: libahci: devslp fixes Srinivas Pandruvada
2018-07-30 15:22 ` Tejun Heo
2018-07-30 15:26 ` Hans de Goede [this message]
2018-07-30 17:33 ` Tejun Heo
2019-03-07 20:27 ` Gwendal Grignou
2019-03-07 20:37 ` Hans de Goede
2019-03-07 23:07 ` Rajat Jain
2019-03-08 0:04 ` Srinivas Pandruvada
2019-03-08 8:57 ` Hans de Goede
2019-03-08 19:29 ` Rajat Jain
2019-03-11 7:52 ` Gwendal Grignou
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=bf4b860c-6f82-4a3f-8b81-5f5c93f4389e@redhat.com \
--to=hdegoede@redhat.com \
--cc=alan.cox@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tj@kernel.org \
/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).