From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme-4.17 round 2
Date: Thu, 12 Apr 2018 08:57:59 -0600 [thread overview]
Message-ID: <7dfd5bdd-3a0b-b131-e44c-b99f54afa3a8@kernel.dk> (raw)
In-Reply-To: <20180412145526.GC4810@localhost.localdomain>
On 4/12/18 8:55 AM, Keith Busch wrote:
> The following changes since commit f23f5bece686a76598335141a091934f7eb0998c:
>
> blk-mq: Allow PCI vector offset for mapping queues (2018-03-27 21:25:36 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-4.17-2
>
> for you to fetch changes up to 1d3528abf41ae3a0ee22f23f294033e000d3ecd1:
>
> nvme: expand nvmf_check_if_ready checks (2018-04-12 07:12:09 -0600)
>
> ----------------------------------------------------------------
> Arnd Bergmann (1):
> nvme: target: fix buffer overflow
>
> Daniel Verkamp (1):
> nvmet: fix space padding in serial number
>
> James Smart (1):
> nvme: expand nvmf_check_if_ready checks
>
> Johannes Thumshirn (2):
> nvme: unexport nvme_start_keep_alive
> nvme: don't send keep-alives to the discovery controller
>
> Keith Busch (4):
> nvme-pci: Skip queue deletion if there are no queues
> nvme-pci: Remove unused queue parameter
> nvme-pci: Separate IO and admin queue IRQ vectors
> nvme: Use admin command effects for admin commands
>
> Matias Bj?rling (1):
> nvme: enforce 64bit offset for nvme_get_log_ext fn
>
> Max Gurtovoy (1):
> nvme: check return value of init_srcu_struct function
>
> Ming Lei (1):
> nvme-loop: fix kernel oops in case of unhandled command
>
> Rodrigo R. Galvao (1):
> nvmet: Fix nvmet_execute_write_zeroes sector count
>
> drivers/nvme/host/core.c | 33 ++++++++++------
> drivers/nvme/host/fabrics.c | 83 ++++++++++++++++++++++++++++++++++++++++-
> drivers/nvme/host/fabrics.h | 33 +---------------
> drivers/nvme/host/fc.c | 12 ++----
> drivers/nvme/host/nvme.h | 4 +-
> drivers/nvme/host/pci.c | 35 ++++++++++-------
> drivers/nvme/host/rdma.c | 14 +------
> drivers/nvme/target/admin-cmd.c | 1 +
> drivers/nvme/target/discovery.c | 2 +-
> drivers/nvme/target/io-cmd.c | 4 +-
> drivers/nvme/target/loop.c | 20 ++--------
> 11 files changed, 141 insertions(+), 100 deletions(-)
This doesn't merge cleanly with my for-linus, or master. Can you
respin this? Just send me the patch series, that's also fine.
--
Jens Axboe
next prev parent reply other threads:[~2018-04-12 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:55 [GIT PULL] nvme-4.17 round 2 Keith Busch
2018-04-12 14:57 ` Jens Axboe [this message]
2018-04-12 15:03 ` 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=7dfd5bdd-3a0b-b131-e44c-b99f54afa3a8@kernel.dk \
--to=axboe@kernel.dk \
/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