From: Eric Blake <eblake@redhat.com>
To: josef@toxicpanda.com, linux-block@vger.kernel.org, nbd@other.debian.org
Cc: philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
christoph.boehmwalder@linbit.com, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] nbd: s/handle/cookie/
Date: Fri, 17 Mar 2023 15:27:44 -0500 [thread overview]
Message-ID: <20230317202749.419094-1-eblake@redhat.com> (raw)
v1 was here: https://lkml.org/lkml/2023/3/10/1162
since then:
- split original 1/3 into 1/5 and 5/5
- new patch 2/5
- reorder members of anon union
- always send cookie in network order
Eric Blake (5):
uapi nbd: improve doc links to userspace spec
block nbd: send handle in network order
uapi nbd: add cookie alias to handle
block nbd: use req.cookie instead of req.handle
docs nbd: userspace NBD now favors github over sourceforge
Documentation/admin-guide/blockdev/nbd.rst | 2 +-
drivers/block/nbd.c | 6 +++---
include/uapi/linux/nbd.h | 25 +++++++++++++++++-----
3 files changed, 24 insertions(+), 9 deletions(-)
base-commit: 8d3c682a5e3d9dfc2448ecbb22f4cd48359b9e21
--
2.39.2
next reply other threads:[~2023-03-17 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 20:27 Eric Blake [this message]
2023-03-17 20:27 ` [PATCH v2 1/5] uapi nbd: improve doc links to userspace spec Eric Blake
2023-03-17 20:27 ` [PATCH v2 2/5] block nbd: send handle in network order Eric Blake
2023-03-20 23:20 ` Ming Lei
2023-03-21 13:59 ` Eric Blake
2023-03-22 0:47 ` Ming Lei
2023-03-22 12:29 ` Eric Blake
2023-03-22 13:23 ` Ming Lei
2023-03-17 20:27 ` [PATCH v2 3/5] uapi nbd: add cookie alias to handle Eric Blake
2023-03-17 20:27 ` [PATCH v2 4/5] block nbd: use req.cookie instead of req.handle Eric Blake
2023-03-17 20:27 ` [PATCH v2 5/5] docs nbd: userspace NBD now favors github over sourceforge Eric Blake
2023-03-22 14:15 ` [PATCH v2 0/5] nbd: s/handle/cookie/ Josef Bacik
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=20230317202749.419094-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=christoph.boehmwalder@linbit.com \
--cc=corbet@lwn.net \
--cc=josef@toxicpanda.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=philipp.reisner@linbit.com \
/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