From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for 5.5-rc
Date: Thu, 9 Jan 2020 14:23:13 -0700 [thread overview]
Message-ID: <5a92249f-63b9-d1e2-0b05-4ae9fcebf4d3@kernel.dk> (raw)
In-Reply-To: <20200109205007.GA17148@redsun51.ssa.fujisawa.hgst.com>
On 1/9/20 1:50 PM, Keith Busch wrote:
> Hi Jens,
>
> We've recovered from the holidays and collecting fixes again. Here are
> two that have been pending for some time. Please pull.
>
> The following changes since commit 802ca0381befe29ba0783e08e3369f9e87ef9d0d:
>
> fs: move guard_bio_eod() after bio_set_op_attrs (2020-01-05 17:45:33 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-5.5-rc
>
> for you to fetch changes up to c2740eb04cd0c713c71727245f52b5cc140a16fb:
>
> nvmet: fix per feat data len for get_feature (2020-01-09 07:54:50 -0800)
>
> ----------------------------------------------------------------
> Amit Engel (1):
> nvmet: fix per feat data len for get_feature
>
> Keith Busch (1):
> nvme: Translate more status codes to blk_status_t
>
> drivers/nvme/host/core.c | 2 ++
> drivers/nvme/target/admin-cmd.c | 12 +++++++++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
Thanks - applied manually, as I rebased the block-5.5 branch to fixup a
patch.
--
Jens Axboe
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-01-09 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 20:50 [GIT PULL] nvme fixes for 5.5-rc Keith Busch
2020-01-09 21:23 ` 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=5a92249f-63b9-d1e2-0b05-4ae9fcebf4d3@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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