From: Farhan Ali <alifm@linux.ibm.com>
To: cohuck@redhat.com, farman@linux.ibm.com, pasic@linux.ibm.com
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, alifm@linux.ibm.com
Subject: [PATCH v3 0/5] Some vfio-ccw fixes
Date: Thu, 11 Jul 2019 10:28:50 -0400 [thread overview]
Message-ID: <cover.1562854091.git.alifm@linux.ibm.com> (raw)
Hi,
While trying to chase down the problem regarding the stacktraces,
I have also found some minor problems in the code.
Would appreciate any review or feedback regarding them.
Thanks
Farhan
ChangeLog
---------
v2 -> v3
- Minor changes as suggested by Conny
- Add Conny's reviewed-by tags
- Add fixes tag for patch 4 and patch 5
v1 -> v2
- Update docs for csch/hsch since we can support those
instructions now (patch 5)
- Fix the memory leak where we fail to free a ccwchain (patch 2)
- Add fixes tag where appropriate.
- Fix comment instead of the order when setting orb.cmd.c64 (patch 1)
Farhan Ali (5):
vfio-ccw: Fix misleading comment when setting orb.cmd.c64
vfio-ccw: Fix memory leak and don't call cp_free in cp_init
vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn
vfio-ccw: Don't call cp_free if we are processing a channel program
vfio-ccw: Update documentation for csch/hsch
Documentation/s390/vfio-ccw.rst | 31 ++++++++++++++++++++++++++++---
drivers/s390/cio/vfio_ccw_cp.c | 28 +++++++++++++++++-----------
drivers/s390/cio/vfio_ccw_drv.c | 2 +-
3 files changed, 46 insertions(+), 15 deletions(-)
--
2.7.4
next reply other threads:[~2019-07-11 14:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:28 Farhan Ali [this message]
2019-07-11 14:28 ` [PATCH v3 1/5] vfio-ccw: Fix misleading comment when setting orb.cmd.c64 Farhan Ali
2019-07-11 20:30 ` Eric Farman
2019-07-11 14:28 ` [PATCH v3 2/5] vfio-ccw: Fix memory leak and don't call cp_free in cp_init Farhan Ali
2019-07-11 20:30 ` Eric Farman
2019-07-12 11:26 ` Cornelia Huck
2019-07-11 14:28 ` [PATCH v3 3/5] vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn Farhan Ali
2019-07-11 14:28 ` [PATCH v3 4/5] vfio-ccw: Don't call cp_free if we are processing a channel program Farhan Ali
2019-07-12 13:19 ` Eric Farman
2019-07-11 14:28 ` [PATCH v3 5/5] vfio-ccw: Update documentation for csch/hsch Farhan Ali
2019-07-12 11:30 ` Cornelia Huck
2019-07-12 13:27 ` Farhan Ali
2019-07-12 13:28 ` Eric Farman
2019-07-15 13:07 ` [PATCH v3 0/5] Some vfio-ccw fixes Cornelia Huck
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.1562854091.git.alifm@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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 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.