From: "Eugenio Pérez" <eperezma@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH 0/1] vdpa: Make ncs autofree
Date: Mon, 14 Feb 2022 20:34:14 +0100 [thread overview]
Message-ID: <20220214193415.1606752-1-eperezma@redhat.com> (raw)
Trivial patch extracted from [1] series. It helps to simplify the memory
management of the function when adding exit paths following the qemu
guidelines.
Thanks!
[1] https://patchwork.kernel.org/project/qemu-devel/patch/20220121202733.404989-30-eperezma@redhat.com/
Eugenio Pérez (1):
vdpa: Make ncs autofree
net/vhost-vdpa.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.27.0
next reply other threads:[~2022-02-14 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:34 Eugenio Pérez [this message]
2022-02-14 19:34 ` [PATCH 1/1] vdpa: Make ncs autofree Eugenio Pérez
2022-02-14 22:14 ` Philippe Mathieu-Daudé via
2022-02-15 3:04 ` Jason Wang
2022-02-16 8:41 ` Stefano Garzarella
2022-02-22 0:34 ` Laurent Vivier
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=20220214193415.1606752-1-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).