From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Nir Soffer" <nsoffer@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"open list:Network Block Dev..." <qemu-block@nongnu.org>
Subject: [PULL 1/4] nbd/server.c: Remove unused field
Date: Fri, 28 Jan 2022 17:00:00 -0600 [thread overview]
Message-ID: <20220128230003.1114719-2-eblake@redhat.com> (raw)
In-Reply-To: <20220128230003.1114719-1-eblake@redhat.com>
From: Nir Soffer <nsoffer@redhat.com>
NBDRequestData struct has unused QSIMPLEQ_ENTRY field. It seems that
this field exists since the first git commit and was never used.
Signed-off-by: Nir Soffer <nsoffer@redhat.com>
Message-Id: <20220111194313.581486-1-nsoffer@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Fixes: d9a73806 ("qemu-nbd: introduce NBDRequest", v1.1)
Signed-off-by: Eric Blake <eblake@redhat.com>
---
nbd/server.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/nbd/server.c b/nbd/server.c
index 4630dd732250..9fb2f264023e 100644
--- a/nbd/server.c
+++ b/nbd/server.c
@@ -77,7 +77,6 @@ static int system_errno_to_nbd_errno(int err)
typedef struct NBDRequestData NBDRequestData;
struct NBDRequestData {
- QSIMPLEQ_ENTRY(NBDRequestData) entry;
NBDClient *client;
uint8_t *data;
bool complete;
--
2.34.1
next prev parent reply other threads:[~2022-01-28 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 22:59 [PULL 0/4] NBD patches for 2022-01-28 Eric Blake
2022-01-28 23:00 ` Eric Blake [this message]
2022-01-28 23:00 ` [PULL 2/4] qapi/block: Cosmetic change in BlockExportType schema Eric Blake
2022-01-28 23:00 ` [PULL 3/4] block/io: Update BSC only if want_zero is true Eric Blake
2022-01-28 23:00 ` [PULL 4/4] iotests/block-status-cache: New test Eric Blake
2022-01-30 15:08 ` [PULL 0/4] NBD patches for 2022-01-28 Peter Maydell
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=20220128230003.1114719-2-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).