From: Kevin Wolf <kwolf@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>,
Hanna Czenczek <hreitz@redhat.com>
Subject: Re: [PULL 0/4] Block layer patches
Date: Thu, 26 Mar 2026 13:50:18 +0100 [thread overview]
Message-ID: <acUripAsWiW-YOR9@redhat.com> (raw)
In-Reply-To: <db795759-2751-4321-9315-c6840be7d030@tls.msk.ru>
Am 26.03.2026 um 06:02 hat Michael Tokarev geschrieben:
> On 24.03.2026 21:56, Kevin Wolf wrote:
>
> > ----------------------------------------------------------------
> > Block layer patches
> >
> > - linux-aio/io-uring: Resubmit tails of short reads/writes
> > - curl: Fix memory leak
> >
> > ----------------------------------------------------------------
> > GuoHan Zhao (1):
> > block/curl: free s->password in cleanup paths
> >
> > Hanna Czenczek (3):
> > linux-aio: Put all parameters into qemu_laiocb
> > linux-aio: Resubmit tails of short reads/writes
> > io-uring: Resubmit tails of short writes
>
> Shouldn't all of this pull req be picked up for the stable series?
I don't think any of these are very critical, but they are fixes (as
should be everything merged during freeze) and have existed in previous
releases, so yes, in that sense they are certainly suitable for stable.
Kevin
next prev parent reply other threads:[~2026-03-26 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 18:56 [PULL 0/4] Block layer patches Kevin Wolf
2026-03-24 18:56 ` [PULL 1/4] block/curl: free s->password in cleanup paths Kevin Wolf
2026-03-24 18:56 ` [PULL 2/4] linux-aio: Put all parameters into qemu_laiocb Kevin Wolf
2026-03-24 18:56 ` [PULL 3/4] linux-aio: Resubmit tails of short reads/writes Kevin Wolf
2026-03-24 18:56 ` [PULL 4/4] io-uring: Resubmit tails of short writes Kevin Wolf
2026-03-25 16:52 ` [PULL 0/4] Block layer patches Peter Maydell
2026-03-26 5:02 ` Michael Tokarev
2026-03-26 12:50 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-25 16:16 Kevin Wolf
2025-11-25 19:29 ` Richard Henderson
2025-04-25 17:52 Kevin Wolf
2025-04-28 17:56 ` Stefan Hajnoczi
2025-04-08 13:00 Kevin Wolf
2025-04-09 8:31 ` Stefan Hajnoczi
2023-11-28 14:09 Kevin Wolf
2023-03-28 12:35 Kevin Wolf
2023-03-28 19:42 ` Peter Maydell
2019-09-20 16:20 Kevin Wolf
2019-09-23 9:49 ` Peter Maydell
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=acUripAsWiW-YOR9@redhat.com \
--to=kwolf@redhat.com \
--cc=hreitz@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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