From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 5.17
Date: Thu, 10 Feb 2022 08:42:09 +0100 [thread overview]
Message-ID: <YgTB0csAbKyI5WvN@infradead.org> (raw)
The following changes since commit b13e0c71856817fca67159b11abac350e41289f5:
block: bio-integrity: Advance seed correctly for larger interval sizes (2022-02-03 21:09:24 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.17-2022-02-10
for you to fetch changes up to 63573807b27e0faf8065a28b1bbe1cbfb23c0130:
nvme-tcp: fix bogus request completion when failing to send AER (2022-02-09 14:50:42 +0100)
----------------------------------------------------------------
nvme fixes for Linux 5.17
- nvme-tcp: fix bogus request completion when failing to send AER
(Sagi Grimberg)
- add the missing nvme_complete_req tracepoint for batched completion
(Bean Huo)
----------------------------------------------------------------
Bean Huo (1):
nvme: add nvme_complete_req tracepoint for batched completion
Sagi Grimberg (1):
nvme-tcp: fix bogus request completion when failing to send AER
drivers/nvme/host/core.c | 1 +
drivers/nvme/host/tcp.c | 10 +++++++++-
2 files changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2022-02-10 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 7:42 Christoph Hellwig [this message]
2022-02-10 13:57 ` [GIT PULL] nvme fixes for Linux 5.17 Jens Axboe
2022-02-22 17:21 ` Christoph Hellwig
2022-02-22 17:26 ` Jens Axboe
2022-02-22 17:29 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 7:33 Christoph Hellwig
2022-02-24 14:03 ` Jens Axboe
2022-02-03 19:35 Christoph Hellwig
2022-02-03 19:38 ` Jens Axboe
2022-01-27 7:19 Christoph Hellwig
2022-01-27 13:53 ` Jens Axboe
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=YgTB0csAbKyI5WvN@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--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 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.