From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de,
Chaitanya.Kulkarni@wdc.com, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme for 5.6-rc
Date: Fri, 14 Feb 2020 10:12:34 -0700 [thread overview]
Message-ID: <442966ed-d371-409c-45c0-0ec473c1ef5e@kernel.dk> (raw)
In-Reply-To: <20200214170939.GB10757@redsun51.ssa.fujisawa.hgst.com>
On 2/14/20 10:09 AM, Keith Busch wrote:
> The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
>
> Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-5.6-rc
>
> for you to fetch changes up to 4c8337a0b7bb7fe7ffd75a7be2aa40804442cf16:
>
> nvme: fix the parameter order for nvme_get_log in nvme_get_fw_slot_info (2020-02-14 23:24:23 +0900)
>
> ----------------------------------------------------------------
> Anton Eidelman (1):
> nvme/tcp: fix bug on double requeue when send fails
>
> Keith Busch (1):
> nvme/pci: move cqe check after device shutdown
>
> Nigel Kirkland (1):
> nvme: prevent warning triggered by nvme_stop_keep_alive
>
> Yi Zhang (1):
> nvme: fix the parameter order for nvme_get_log in nvme_get_fw_slot_info
>
> drivers/nvme/host/core.c | 12 ++++++------
> drivers/nvme/host/pci.c | 23 ++++++++++++++++++-----
> drivers/nvme/host/rdma.c | 2 +-
> drivers/nvme/host/tcp.c | 9 +++++++--
> 4 files changed, 32 insertions(+), 14 deletions(-)
Applied manually, as your branch is way ahead of block-5.6. I'll rebase
the branch once this is in, so we're more up-to-date.
--
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-02-14 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:09 [GIT PULL] nvme for 5.6-rc Keith Busch
2020-02-14 17:12 ` 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=442966ed-d371-409c-45c0-0ec473c1ef5e@kernel.dk \
--to=axboe@kernel.dk \
--cc=Chaitanya.Kulkarni@wdc.com \
--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;
as well as URLs for NNTP newsgroup(s).