From: Jens Axboe <axboe@kernel.dk>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-nvme <linux-nvme@lists.infradead.org>,
Keith Busch <keith.busch@intel.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Christoph Hellwig <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH v2 0/2] nvme APST quirk updates, take two
Date: Thu, 20 Apr 2017 11:08:00 -0600 [thread overview]
Message-ID: <dec142aa-ffd8-984e-adcc-f0e6bf0a4e0b@kernel.dk> (raw)
In-Reply-To: <CALCETrUQ_npTbm7eEeoFJP3V9y-keq9bjS0hD+t=k-AXSDMteA@mail.gmail.com>
On 04/20/2017 11:06 AM, Andy Lutomirski wrote:
>
>
> On Apr 20, 2017 9:38 AM, "Jens Axboe" <axboe@kernel.dk <mailto:axboe@kernel.dk>> wrote:
>
> On 04/20/2017 10:30 AM, Jens Axboe wrote:
> > On 04/20/2017 10:29 AM, Keith Busch wrote:
> >> 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 <mailto:keith.busch@intel.com>>
> >
> > Great, I have queued it up.
>
> Spoke too soon. Andy, did you compile this?
>
> drivers/nvme/host/core.c: In function ‘nvme_init_identify’:
> drivers/nvme/host/core.c:1524:6: error: ‘force_apst’ undeclared (first use in this function)
> if (force_apst && (ctrl->quirks & NVME_QUIRK_NO_DEEPEST_PS)) {
> ^~~~~~~~~~
> drivers/nvme/host/core.c:1524:6: note: each undeclared identifier is reported only once for each function it appears in
>
> No, you did not.
>
>
> I compiled the end result but not the middle. D'oh. Better version coming in an hour or two.
This is from the end-result. I think you compiled the previous series,
but not the revised v2 one you sent out. Because none of those patches
add force_apst.
--
Jens Axboe
next prev parent reply other threads:[~2017-04-20 17:08 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
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 [this message]
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=dec142aa-ffd8-984e-adcc-f0e6bf0a4e0b@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@amacapital.net \
--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