From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: jhansen@vmware.com, vdasa@vmware.com, arnd@arndb.de,
gregkh@linuxfoundation.org, acking@vmware.com, dtor@vmware.com
Cc: pv-drivers@vmware.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/3] VMCI: Various fixes
Date: Thu, 10 Feb 2022 23:26:55 +0100 [thread overview]
Message-ID: <cover.1644531317.git.christophe.jaillet@wanadoo.fr> (raw)
Patch 1 and 2 should be straighforward.
But review with much more care the 3rd one, as explained below the --- in the
patch.
Christophe JAILLET (3):
VMCI: Fix the description of vmci_check_host_caps()
VMCI: No need to clear memory after a dma_alloc_coherent() call
VMCI: Fix some error handling paths in vmci_guest_probe_device()
drivers/misc/vmw_vmci/vmci_guest.c | 30 ++++++++++++++----------------
1 file changed, 14 insertions(+), 16 deletions(-)
--
2.32.0
next reply other threads:[~2022-02-10 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 22:26 Christophe JAILLET [this message]
2022-02-10 22:27 ` [PATCH 1/3] VMCI: Fix the description of vmci_check_host_caps() Christophe JAILLET
2022-02-17 7:08 ` Vishnu Dasa
2022-02-10 22:27 ` [PATCH 2/3] VMCI: No need to clear memory after a dma_alloc_coherent() call Christophe JAILLET
2022-02-17 7:10 ` Vishnu Dasa
2022-02-10 22:27 ` [PATCH 3/3] VMCI: Fix some error handling paths in vmci_guest_probe_device() Christophe JAILLET
2022-02-11 14:09 ` Dan Carpenter
2022-02-11 20:06 ` Christophe JAILLET
2022-02-24 6:53 ` Vishnu Dasa
2022-02-24 10:03 ` Dan Carpenter
2022-02-24 16:08 ` Vishnu Dasa
2022-02-24 0:43 ` Vishnu Dasa
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=cover.1644531317.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=acking@vmware.com \
--cc=arnd@arndb.de \
--cc=dtor@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhansen@vmware.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=vdasa@vmware.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