From: Keith Busch <keith.busch@intel.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Jens Axboe <axboe@kernel.dk>, Andy Lutomirski <luto@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 0/2] nvme APST quirk updates, take two
Date: Thu, 20 Apr 2017 12:29:25 -0400 [thread overview]
Message-ID: <20170420162925.GB25259@localhost.localdomain> (raw)
In-Reply-To: <b6da572f-2c50-81b4-64b0-73abdd124408@grimberg.me>
On Thu, Apr 20, 2017 at 07:15:15PM +0300, Sagi Grimberg wrote:
>
> > > Hi Jens-
> > >
> > > These are just the quirk updates, split out. The patches are
> > > unchanged.
> > >
> > > I think that, even if we want to apply a broader quirk for 4.11, we
> > > should still apply these so that we can cleanly revert the broader
> > > quirk later. IOW, let's get the known regressions fixed before we
> > > get too excited about the unknown regressions.
> >
> > This looks good to me, and 4.11 appropriate. I'll expedite this
> > through the block tree, if Keith/Sagi/Christoph agrees on this
> > being the right approach for 4.11.
>
> I'm perfectly fine with this going to 4.11
All good with me as well.
Reviewed-by: Keith Busch <keith.busch@intel.com>
next prev parent reply other threads:[~2017-04-20 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 16:11 [PATCH v2 0/2] nvme APST quirk updates, take two Andy Lutomirski
2017-04-20 16:11 ` [PATCH v2 1/2] nvme: Adjust the Samsung APST quirk Andy Lutomirski
2017-04-20 16:11 ` [PATCH v2 2/2] nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA" Andy Lutomirski
2017-04-20 16:13 ` [PATCH v2 0/2] nvme APST quirk updates, take two Jens Axboe
2017-04-20 16:15 ` Sagi Grimberg
2017-04-20 16:29 ` Keith Busch [this message]
2017-04-20 16:30 ` Jens Axboe
2017-04-20 16:38 ` Jens Axboe
[not found] ` <CALCETrUQ_npTbm7eEeoFJP3V9y-keq9bjS0hD+t=k-AXSDMteA@mail.gmail.com>
2017-04-20 17:08 ` Jens Axboe
2017-04-20 18:56 ` Andy Lutomirski
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=20170420162925.GB25259@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kai.heng.feng@canonical.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