From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: keith.busch@intel.com, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [GIT PULL] NVMe fixes for 4.10-rc4
Date: Wed, 11 Jan 2017 11:47:29 -0700 [thread overview]
Message-ID: <d5fc380b-446e-ca0b-6e1f-38588521a8ce@kernel.dk> (raw)
In-Reply-To: <20170111184236.GA21620@infradead.org>
On 01/11/2017 11:42 AM, Christoph Hellwig wrote:
> Hi Jens,
>
> below are two small NVMe fixes for this merge window.
>
> The following changes since commit 6bf6b0aa3da84a3d9126919a94c49c0fb7ee2fb3:
>
> virtio_blk: fix panic in initialization error path (2017-01-10 13:30:50 -0700)
>
> are available in the git repository at:
>
> git://git.infradead.org/nvme.git nvme-4.10-fixes
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2017-01-11 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 18:42 [GIT PULL] NVMe fixes for 4.10-rc4 Christoph Hellwig
2017-01-11 18:47 ` 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=d5fc380b-446e-ca0b-6e1f-38588521a8ce@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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