From: Eric Farman <farman@linux.ibm.com>
To: stable@vger.kernel.org
Cc: Eric Farman <farman@linux.ibm.com>
Subject: [PATCH 6.6.y v2 0/4] s390/vfio-ccw stable fixes
Date: Fri, 21 Aug 2026 13:49:47 -0400 [thread overview]
Message-ID: <20260821174951.3467637-1-farman@linux.ibm.com> (raw)
Hi,
The recent s390/vfio-ccw fixes applied to linux-6.6.y had a build error
on the first patch, and some merge conflicts on three others.
I fixed/resubmitted the other three yesterday, but neglected to notice
the build error presented on the first patch.
Here are those all fixed together (I hope). Built on top of the current
stable queue that includes the other fixes.
Eric Farman (4):
s390/vfio_ccw: Free all memory if cp_init() fails
s390/vfio_ccw: Ensure first IDAW remains constant
s390/vfio_ccw: Calculate idal length based on idaw type
s390/vfio_ccw: Implement a crw lock
drivers/s390/cio/vfio_ccw_chp.c | 26 ++++++++++-------
drivers/s390/cio/vfio_ccw_cp.c | 43 +++++++++++++++++++++++++----
drivers/s390/cio/vfio_ccw_cp.h | 2 ++
drivers/s390/cio/vfio_ccw_drv.c | 6 ++++
drivers/s390/cio/vfio_ccw_ops.c | 4 +++
drivers/s390/cio/vfio_ccw_private.h | 4 +++
6 files changed, 69 insertions(+), 16 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-21 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 17:49 Eric Farman [this message]
2026-08-21 17:49 ` [PATCH 6.6.y v2 1/4] s390/vfio_ccw: Free all memory if cp_init() fails Eric Farman
2026-08-21 17:49 ` [PATCH 6.6.y v2 2/4] s390/vfio_ccw: Ensure first IDAW remains constant Eric Farman
2026-08-21 17:49 ` [PATCH 6.6.y v2 3/4] s390/vfio_ccw: Calculate idal length based on idaw type Eric Farman
2026-08-21 17:49 ` [PATCH 6.6.y v2 4/4] s390/vfio_ccw: Implement a crw lock Eric Farman
2026-08-25 11:49 ` [PATCH 6.6.y v2 0/4] s390/vfio-ccw stable fixes Sasha Levin
2026-08-25 13:27 ` Eric Farman
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=20260821174951.3467637-1-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=stable@vger.kernel.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