All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Song Gao <gaosong@loongson.cn>
Cc: qemu-devel@nongnu.org, stefanha@gmail.com
Subject: Re: [PULL 00/10] loongarch-to-apply queue
Date: Mon, 6 Nov 2023 22:22:40 +0800	[thread overview]
Message-ID: <20231106142240.GA929013@fedora> (raw)
In-Reply-To: <20231103062332.2413724-1-gaosong@loongson.cn>

[-- Attachment #1: Type: text/plain, Size: 115 bytes --]

Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/8.2 for any user-visible changes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2023-11-06 14:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  6:23 [PULL 00/10] loongarch-to-apply queue Song Gao
2023-11-03  6:23 ` [PULL 01/10] target/loongarch: Add cpu model 'max' Song Gao
2023-11-03  6:23 ` [PULL 02/10] target/loongarch: Allow user enable/disable LSX/LASX features Song Gao
2023-11-03  6:23 ` [PULL 03/10] target/loongarch: Implement query-cpu-model-expansion Song Gao
2023-11-03  6:23 ` [PULL 04/10] target/loongarch: Support 4K page size Song Gao
2023-11-03  6:23 ` [PULL 05/10] linux-user/loongarch64: Use traps to track LSX/LASX usage Song Gao
2023-11-03  6:23 ` [PULL 06/10] linux-user/loongarch64: Fix setup_extcontext alloc wrong fpu_context size Song Gao
2023-11-03  6:23 ` [PULL 07/10] linux-user/loongarch64: setup_sigframe() set 'end' context size 0 Song Gao
2023-11-03  6:23 ` [PULL 08/10] linux-user/loongarch64: Use abi_{ulong,uint} types Song Gao
2023-11-03  6:23 ` [PULL 09/10] linux-user/loongarch64: Add LSX sigcontext save/restore Song Gao
2023-11-03  6:23 ` [PULL 10/10] linux-user/loongarch64: Add LASX " Song Gao
2023-11-06 14:22 ` Stefan Hajnoczi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-23  1:46 [PULL 00/10] loongarch-to-apply queue Song Gao
2024-05-23 16:44 ` Richard Henderson

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=20231106142240.GA929013@fedora \
    --to=stefanha@redhat.com \
    --cc=gaosong@loongson.cn \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.