From: Jens Axboe <axboe@kernel.dk>
To: Andy Lutomirski <luto@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
linux-nvme <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/3] nvme: APST improvements (for 4.12, perhaps)
Date: Mon, 24 Apr 2017 22:04:02 -0600 [thread overview]
Message-ID: <20170425040400.GB23572@kernel.dk> (raw)
In-Reply-To: <cover.1492816561.git.luto@kernel.org>
On Fri, Apr 21 2017, Andy Lutomirski wrote:
> Hi all-
>
> These are APST improvements for 4.12 or so. The first one fixes a
> buggy comment. The second makes debugging easier. The third makes
> it possible to force APST on despite quirks.
>
> Andy Lutomirski (3):
> nvme: Fix APST comment
> nvme: Display raw APST configuration via DYNAMIC_DEBUG
> nvme: Add nvme_core.force_apst to ignore the NO_APST quirk
>
> drivers/nvme/host/core.c | 38 ++++++++++++++++++++++++++++++++++++--
> 1 file changed, 36 insertions(+), 2 deletions(-)
I have added these for 4.12, thanks Andy.
--
Jens Axboe
next prev parent reply other threads:[~2017-04-25 4:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 23:19 [PATCH 0/3] nvme: APST improvements (for 4.12, perhaps) Andy Lutomirski
2017-04-21 23:19 ` [PATCH 1/3] nvme: Fix APST comment Andy Lutomirski
2017-04-23 8:12 ` Christoph Hellwig
2017-04-21 23:19 ` [PATCH 2/3] nvme: Display raw APST configuration via DYNAMIC_DEBUG Andy Lutomirski
2017-04-23 8:12 ` Christoph Hellwig
2017-04-21 23:19 ` [PATCH 3/3] nvme: Add nvme_core.force_apst to ignore the NO_APST quirk Andy Lutomirski
2017-04-23 8:12 ` Christoph Hellwig
2017-04-25 4:04 ` Jens Axboe [this message]
2017-04-25 7:19 ` [PATCH 0/3] nvme: APST improvements (for 4.12, perhaps) Christoph Hellwig
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=20170425040400.GB23572@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kai.heng.feng@canonical.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=luto@kernel.org \
--cc=sagi@grimberg.me \
/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).