From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Keith Busch <keith.busch@intel.com>,
stable@vger.kernel.org,
Charles Machalow <charles.machalow@intel.com>,
hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [PATCH] Fix controller reset return
Date: Fri, 25 May 2018 16:55:12 +0200 [thread overview]
Message-ID: <20180525145512.GA27143@lst.de> (raw)
In-Reply-To: <20180525145009.GR11037@localhost.localdomain>
On Fri, May 25, 2018 at 08:50:09AM -0600, Keith Busch wrote:
> On Fri, May 25, 2018 at 02:10:56AM -0700, Christoph Hellwig wrote:
> > Thanks,
> >
> > applied to nvme-4.18-2
>
> I'd included this one in an earlier 4.17 pull request. The regression
> caused some major problems in test automation, and the fix was trivial.
ok, I'll drop it again to avoid a duplicate commit.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] Fix controller reset return
Date: Fri, 25 May 2018 16:55:12 +0200 [thread overview]
Message-ID: <20180525145512.GA27143@lst.de> (raw)
In-Reply-To: <20180525145009.GR11037@localhost.localdomain>
On Fri, May 25, 2018@08:50:09AM -0600, Keith Busch wrote:
> On Fri, May 25, 2018@02:10:56AM -0700, Christoph Hellwig wrote:
> > Thanks,
> >
> > applied to nvme-4.18-2
>
> I'd included this one in an earlier 4.17 pull request. The regression
> caused some major problems in test automation, and the fix was trivial.
ok, I'll drop it again to avoid a duplicate commit.
next prev parent reply other threads:[~2018-05-25 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 16:25 [PATCH] Fix controller reset return Keith Busch
2018-05-11 16:25 ` Keith Busch
2018-05-11 16:36 ` Keith Busch
2018-05-11 16:36 ` Keith Busch
2018-05-25 9:10 ` Christoph Hellwig
2018-05-25 9:10 ` Christoph Hellwig
2018-05-25 14:50 ` Keith Busch
2018-05-25 14:50 ` Keith Busch
2018-05-25 14:55 ` Christoph Hellwig [this message]
2018-05-25 14:55 ` 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=20180525145512.GA27143@lst.de \
--to=hch@lst.de \
--cc=charles.machalow@intel.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=keith.busch@linux.intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.