qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>, Helge Deller <deller@gmx.de>,
	Sven Schnelle <svens@stackframe.org>
Cc: qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PULL 0/9] target/hppa fixes for 9.0
Date: Fri, 22 Mar 2024 07:36:58 -1000	[thread overview]
Message-ID: <125cb191-bb3f-4ea6-b3ef-02476d4a47ab@linaro.org> (raw)
In-Reply-To: <f4682acd-129c-4695-994d-1cd2cd8a842c@tls.msk.ru>

On 3/21/24 18:48, Michael Tokarev wrote:
> 21.03.2024 21:32, Helge Deller wrote:
>> On 3/21/24 19:25, Sven Schnelle wrote:
>>> Michael Tokarev <mjt@tls.msk.ru> writes:
>>>
>>>> 20.03.2024 03:32, Richard Henderson :
>>>>
>>>>> Richard Henderson (3):
>>>>>         target/hppa: Fix assemble_16 insns for wide mode
>>>>>         target/hppa: Fix assemble_11a insns for wide mode
>>>>>         target/hppa: Fix assemble_12a insns for wide mode
>>>>> Sven Schnelle (6):
>>>>>         target/hppa: ldcw,s uses static shift of 3
>>>>>         target/hppa: fix shrp for wide mode
>>>>>         target/hppa: fix access_id check
>>>>>         target/hppa: exit tb on flush cache instructions
>>>>>         target/hppa: mask privilege bits in mfia
>>>>>         target/hppa: fix do_stdby_e()
>>>>
>>>> Is it all -stable material (when appropriate)?
>>>
>>> I'd say yes.
>>
>> Yes.
> 
> Picked all 9 for stable-8.2.
> 
> And none for stable-7.2.  There, just one of them applies.
> 
> I understand most of them can be applied still (it is just adding
> new lines here and there, the same lines needs to be added to 7.2
> but there, context is missing so every patch needs manual applying,
> which I'm not feeling confident doing.  If anything of that is
> really good to have in 7.2 (which has de-facto become an LTS series),
> please re-spin it on top of stable-7.2 branch and send the result
> to qemu-stable@.

This is all for hppa64 support, which was not present in 7.2.

r~



      reply	other threads:[~2024-03-22 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  0:32 [PULL 0/9] target/hppa fixes for 9.0 Richard Henderson
2024-03-20  0:32 ` [PULL 1/9] target/hppa: Fix assemble_16 insns for wide mode Richard Henderson
2024-03-20  0:32 ` [PULL 2/9] target/hppa: Fix assemble_11a " Richard Henderson
2024-03-20  0:32 ` [PULL 3/9] target/hppa: Fix assemble_12a " Richard Henderson
2024-03-20  0:32 ` [PULL 4/9] target/hppa: ldcw,s uses static shift of 3 Richard Henderson
2024-03-20  0:32 ` [PULL 5/9] target/hppa: fix shrp for wide mode Richard Henderson
2024-03-20  0:32 ` [PULL 6/9] target/hppa: fix access_id check Richard Henderson
2024-03-20  0:32 ` [PULL 7/9] target/hppa: exit tb on flush cache instructions Richard Henderson
2024-03-20  0:32 ` [PULL 8/9] target/hppa: mask privilege bits in mfia Richard Henderson
2024-03-20  0:32 ` [PULL 9/9] target/hppa: fix do_stdby_e() Richard Henderson
2024-03-20 15:05 ` [PULL 0/9] target/hppa fixes for 9.0 Peter Maydell
2024-03-21 17:06 ` Michael Tokarev
2024-03-21 18:25   ` Sven Schnelle
2024-03-21 18:32     ` Helge Deller
2024-03-22  4:48       ` Michael Tokarev
2024-03-22 17:36         ` Richard Henderson [this message]

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=125cb191-bb3f-4ea6-b3ef-02476d4a47ab@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=deller@gmx.de \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=svens@stackframe.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;
as well as URLs for NNTP newsgroup(s).