qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Taylor Simpson <ltaylorsimpson@gmail.com>,
	Brian Cain <brian.cain@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, matheus.bernardino@oss.qualcomm.com,
	sid.manning@oss.qualcomm.com, marco.liebel@oss.qualcomm.com,
	richard.henderson@linaro.org, ale@rev.ng, anjo@rev.ng
Subject: Re: [PATCH 0/4] Clean up end-of-instruction processing
Date: Thu, 4 Dec 2025 09:46:39 +0100	[thread overview]
Message-ID: <6ea77767-5442-4868-b9e6-8633a15c5c9b@linaro.org> (raw)
In-Reply-To: <CAATN3Nps8qxYPBHxM6NfP6qt+NSNHzhiC_C-tuK796rQG+qbAQ@mail.gmail.com>

On 17/11/25 19:35, Taylor Simpson wrote:
> 
> They are based on this one
> commit bc831f37398b51dfe65d99a67bcff9352f84a9d2 (origin/staging, origin/ 
> master, origin/HEAD)
> Merge: 76929d6117 7dbe2d7df0
> Author: Richard Henderson <richard.henderson@linaro.org 
> <mailto:richard.henderson@linaro.org>>
> Date:   Tue Oct 28 11:48:05 2025 +0100
> 
> They also apply cleanly to Brian's hex-next-express branch.
> 
> What error are you getting on your end?

Maybe I did something wrong and was based I don't remember where =)

No more issue, sorry for the noise!

> 
> Thanks,
> Taylor
> 
> 
> On Mon, Nov 17, 2025 at 10:08 AM Brian Cain <brian.cain@oss.qualcomm.com 
> <mailto:brian.cain@oss.qualcomm.com>> wrote:
> 
>     Maybe they're based on the other commits on my tree which are queued
>     for inclusion after 10.2? https://github.com/quic/qemu/commits/hex-
>     next-express/ <https://github.com/quic/qemu/commits/hex-next-express/>
> 



  parent reply	other threads:[~2025-12-04  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 23:00 [PATCH 0/4] Clean up end-of-instruction processing Taylor Simpson
2025-11-14 23:00 ` [PATCH 1/4] Hexagon (target/hexagon) Remove gen_log_reg_write Taylor Simpson
2025-12-03 23:34   ` Brian Cain
2025-11-14 23:00 ` [PATCH 2/4] Hexagon (target/hexagon) s/gen_log_pred_write/gen_pred_write Taylor Simpson
2025-11-17 17:35   ` Philippe Mathieu-Daudé
2025-12-03 23:36   ` Brian Cain
2025-11-14 23:00 ` [PATCH 3/4] Hexagon (target/hexagon) s/gen_log_vreg_write/gen_vreg_write Taylor Simpson
2025-11-17 17:36   ` Philippe Mathieu-Daudé
2025-12-03 23:37   ` Brian Cain
2025-11-14 23:00 ` [PATCH 4/4] Hexagon (target/hexagon) s/log_write/gen_write Taylor Simpson
2025-11-17 17:37   ` Philippe Mathieu-Daudé
2025-12-03 23:37   ` Brian Cain
2025-11-17  9:28 ` [PATCH 0/4] Clean up end-of-instruction processing Philippe Mathieu-Daudé
2025-11-17 17:08   ` Brian Cain
2025-11-17 17:35     ` Philippe Mathieu-Daudé
2025-11-17 18:35     ` Taylor Simpson
2025-11-17 20:02       ` Taylor Simpson
2025-12-04  8:46       ` Philippe Mathieu-Daudé [this message]
2025-12-09 19:18 ` Brian Cain

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=6ea77767-5442-4868-b9e6-8633a15c5c9b@linaro.org \
    --to=philmd@linaro.org \
    --cc=ale@rev.ng \
    --cc=anjo@rev.ng \
    --cc=brian.cain@oss.qualcomm.com \
    --cc=ltaylorsimpson@gmail.com \
    --cc=marco.liebel@oss.qualcomm.com \
    --cc=matheus.bernardino@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sid.manning@oss.qualcomm.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 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).