From: hch@lst.de (Christoph Hellwig)
Subject: nvme-4.14 rebased
Date: Wed, 16 Aug 2017 10:13:46 +0200 [thread overview]
Message-ID: <20170816081346.GA18770@lst.de> (raw)
Hi all,
I've rebased the nvme-4.14 branch on top of the nvme-4.13 branch
to avoid conflicts. As part of that I made the timestamp set features
return an error similar to the other reset fixes.
Jon: can you double check the change is correct?
next reply other threads:[~2017-08-16 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 8:13 Christoph Hellwig [this message]
2017-08-11 11:08 ` nvme-4.14 rebased Jon Derrick
2017-08-16 16:07 ` Keith Busch
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=20170816081346.GA18770@lst.de \
--to=hch@lst.de \
/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.