public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: James Wainwright <james.wainwright@lowrisc.org>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org, alistair.francis@wdc.com
Subject: Re: [PATCH v5 0/3] target/riscv: add draft RISC-V Zbr ext as xbr0p93
Date: Wed, 25 Mar 2026 12:25:14 +1000	[thread overview]
Message-ID: <CAKmqyKNTm51Gx4TEL_3nm+8K=mZa8pMfnL1PA9kcqHpq0Uw=ug@mail.gmail.com> (raw)
In-Reply-To: <20260320134254.217123-1-james.wainwright@lowrisc.org>

On Fri, Mar 20, 2026 at 11:44 PM James Wainwright
<james.wainwright@lowrisc.org> wrote:
>
> >  This patch fails checkpatch:
>
> Oops, sorry about that. Fixed the license header but the original
> `crc32c` file didn't have a `MAINTAINER` so I haven't assigned one to
> this new file either. I hope that's okay.
>
> > Please keep previous tags in new versions
>
> Do you mean the `Reviewed-by` lines? I've kept those in this series.
>
> James Wainwright (3):
>   util: export CRC32[C] lookup tables
>   target/riscv: add draft RISC-V Zbr ext as xbr0p93
>   disas: diassemble RISC-V xlrbr (crc32) instructions

Thanks!

Applied to riscv-to-apply.next

Alistair

>
>  MAINTAINERS                               |  5 +-
>  disas/meson.build                         |  3 +-
>  disas/riscv-xlrbr.c                       | 79 ++++++++++++++++++++++
>  disas/riscv-xlrbr.h                       | 19 ++++++
>  disas/riscv.c                             |  2 +
>  include/qemu/crc32.h                      | 14 ++++
>  include/qemu/crc32c.h                     |  1 +
>  target/riscv/bitmanip_helper.c            | 20 ++++++
>  target/riscv/cpu.c                        |  4 +-
>  target/riscv/cpu_cfg.h                    |  1 +
>  target/riscv/cpu_cfg_fields.h.inc         |  1 +
>  target/riscv/helper.h                     |  2 +
>  target/riscv/insn_trans/trans_xlrbr.c.inc | 45 +++++++++++++
>  target/riscv/meson.build                  |  1 +
>  target/riscv/translate.c                  |  3 +
>  target/riscv/xlrbr.decode                 | 30 +++++++++
>  tests/tcg/riscv64/Makefile.softmmu-target |  5 ++
>  tests/tcg/riscv64/test-crc32.S            | 64 ++++++++++++++++++
>  util/crc32.c                              | 81 +++++++++++++++++++++++
>  util/crc32c.c                             |  4 +-
>  util/meson.build                          |  1 +
>  21 files changed, 380 insertions(+), 5 deletions(-)
>  create mode 100644 disas/riscv-xlrbr.c
>  create mode 100644 disas/riscv-xlrbr.h
>  create mode 100644 include/qemu/crc32.h
>  create mode 100644 target/riscv/insn_trans/trans_xlrbr.c.inc
>  create mode 100644 target/riscv/xlrbr.decode
>  create mode 100644 tests/tcg/riscv64/test-crc32.S
>  create mode 100644 util/crc32.c
>
> --
> 2.48.1
>
>


      parent reply	other threads:[~2026-03-25  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 13:42 [PATCH v5 0/3] target/riscv: add draft RISC-V Zbr ext as xbr0p93 James Wainwright
2026-03-20 13:42 ` [PATCH v5 1/3] util: export CRC32[C] lookup tables James Wainwright
2026-03-20 13:42 ` [PATCH v5 2/3] target/riscv: add draft RISC-V Zbr ext as xbr0p93 James Wainwright
2026-03-20 13:42 ` [PATCH v5 3/3] disas: diassemble RISC-V xlrbr (crc32) instructions James Wainwright
2026-03-25  2:25 ` Alistair Francis [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='CAKmqyKNTm51Gx4TEL_3nm+8K=mZa8pMfnL1PA9kcqHpq0Uw=ug@mail.gmail.com' \
    --to=alistair23@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=james.wainwright@lowrisc.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@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