From: Michael Tokarev <mjt@tls.msk.ru>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Laurent Vivier <laurent@vivier.eu>,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>,
Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Subject: Re: [PATCH 1/2] linux-user/s390x: Fix single-stepping SVC
Date: Thu, 11 May 2023 16:50:51 +0300 [thread overview]
Message-ID: <5e772a1c-df27-8d5d-21db-8cf021d64b6e@msgid.tls.msk.ru> (raw)
In-Reply-To: <8c1e5072a92d3160d7f906208e0b9f4c78fdaf84.camel@linux.ibm.com>
11.05.2023 16:45, Ilya Leoshkevich wrote:
>> 11.05.2023 14:20, Ilya Leoshkevich wrote:
>>> While I would personally love to see this in -stable, I don't think it
>>> fits the official criteria - it's not a security fix and it's not a
>>> regression.
> Okay, then let's include it into -stable.
>
> It's just that I'm not too familiar with the QEMU -stable process, so
> I read [1], and it sounded quite strict.
>
> [1] https://www.qemu.org/docs/master/devel/stable-process.html
The text there reads:
If you think the patch would be important for users of
the current release (or for a distribution picking fixes),
it is usually a good candidate for stable.
:)
Please Cc: qemu-stable@nongnu.org the next time you think
something is good to have there.
/mjt
next prev parent reply other threads:[~2023-05-11 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 23:02 [PATCH 0/2] linux-user/s390x: Fix single-stepping SVC Ilya Leoshkevich
2023-05-10 23:02 ` [PATCH 1/2] " Ilya Leoshkevich
2023-05-11 10:55 ` Michael Tokarev
2023-05-11 11:20 ` Ilya Leoshkevich
2023-05-11 12:32 ` Michael Tokarev
2023-05-11 13:45 ` Ilya Leoshkevich
2023-05-11 13:50 ` Michael Tokarev [this message]
2023-05-10 23:02 ` [PATCH 2/2] tests/tcg/s390x: Test " Ilya Leoshkevich
2023-05-11 10:51 ` Alex Bennée
2023-07-07 8:37 ` Thomas Huth
2023-05-31 14:37 ` [PATCH 0/2] linux-user/s390x: Fix " Thomas Huth
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=5e772a1c-df27-8d5d-21db-8cf021d64b6e@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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.