From: Jens Axboe <axboe@fb.com>
To: Christoph Hellwig <hch@lst.de>, Andy Lutomirski <luto@kernel.org>
Cc: Keith Busch <keith.busch@intel.com>,
<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
J Freyensee <james_p_freyensee@linux.intel.com>
Subject: Re: [PATCH v4 0/3] nvme power saving
Date: Sat, 24 Sep 2016 10:55:03 -0600 [thread overview]
Message-ID: <3f54698d-503c-0d2e-7702-1f4f8557582e@fb.com> (raw)
In-Reply-To: <20160923234236.GA19222@lst.de>
On 09/23/2016 05:42 PM, Christoph Hellwig wrote:
> Jens,
>
> can we at least get patches 1 and 2 in while pondering the fate
> of the right interface for patch 3?
>
Yes definitely, I have no beef with the first two patches. I'll add them
for 4.9.
--
Jens Axboe
prev parent reply other threads:[~2016-09-24 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 18:16 Andy Lutomirski
2016-09-16 18:16 ` [PATCH v4 1/3] nvme/scsi: Remove power management support Andy Lutomirski
2016-09-16 23:37 ` J Freyensee
2016-09-16 18:16 ` [PATCH v4 2/3] nvme: Pass pointers, not dma addresses, to nvme_get/set_features() Andy Lutomirski
2016-09-16 18:16 ` [PATCH v4 3/3] nvme: Enable autonomous power state transitions Andy Lutomirski
2016-09-17 0:49 ` [PATCH v4 0/3] nvme power saving J Freyensee
2016-09-22 0:11 ` Andy Lutomirski
2016-09-22 13:21 ` Christoph Hellwig
2016-09-22 14:23 ` Jens Axboe
2016-09-22 20:11 ` Andy Lutomirski
2016-09-22 20:43 ` Jens Axboe
2016-09-22 21:33 ` J Freyensee
2016-09-22 22:15 ` Andy Lutomirski
2016-10-28 0:06 ` Andy Lutomirski
2016-10-28 5:29 ` Christoph Hellwig
2016-09-22 22:16 ` Keith Busch
2016-09-22 22:07 ` Jens Axboe
2016-09-23 23:42 ` Christoph Hellwig
2016-09-24 16:55 ` Jens Axboe [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=3f54698d-503c-0d2e-7702-1f4f8557582e@fb.com \
--to=axboe@fb.com \
--cc=hch@lst.de \
--cc=james_p_freyensee@linux.intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=luto@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
Powered by JetHome