Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Eric Farman <farman@linux.ibm.com>
Subject: Re: [PATCH 6.6.y v2 0/4] s390/vfio-ccw stable fixes
Date: Tue, 25 Aug 2026 07:49:28 -0400	[thread overview]
Message-ID: <202608250006.9e28a4bae2a86a35@kernel.org> (raw)
In-Reply-To: <20260821174951.3467637-1-farman@linux.ibm.com>

On Fri, Aug 21, 2026 at 01:49:47PM -0400, Eric Farman wrote:
> Here are those all fixed together (I hope). Built on top of the current
> stable queue that includes the other fixes.

All four are already in the 6.6 queue, so there was nothing to re-apply
there.

While checking that, I noticed 74186c2968f8 ("s390/vfio_ccw: Free all
memory if cp_init() fails") is missing from 6.1, 5.15 and 5.10 too, so I
queued it there as well - spelled u32 instead of dma32_t, which does not
exist on those trees. Thanks.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2026-08-25 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21 17:49 [PATCH 6.6.y v2 0/4] s390/vfio-ccw stable fixes Eric Farman
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 ` Sasha Levin [this message]
2026-08-25 13:27   ` [PATCH 6.6.y v2 0/4] s390/vfio-ccw stable fixes 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=202608250006.9e28a4bae2a86a35@kernel.org \
    --to=sashal@kernel.org \
    --cc=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