qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [PATCH RESEND 0/2] Resolve some redundant property accessors
Date: Thu, 05 May 2022 16:52:13 +0000	[thread overview]
Message-ID: <A987D65D-940B-4827-B547-92D27FBBA46E@gmail.com> (raw)
In-Reply-To: <20220301225220.239065-1-shentey@gmail.com>

Am 1. März 2022 22:52:18 UTC schrieb Bernhard Beschow <shentey@gmail.com>:
>No changes. Just also CC'ed to qemu-trivial.
>
>The QOM API already provides appropriate accessors, so reuse them.
>
>Testing done:
>
>  :$ make check
>  Ok:                 570
>  Expected Fail:      0
>  Fail:               0
>  Unexpected Pass:    0
>  Skipped:            178
>  Timeout:            0
>
>
>Bernhard Beschow (2):
>  hw/vfio/pci-quirks: Resolve redundant property getters
>  hw/riscv/sifive_u: Resolve redundant property accessors
>
> hw/riscv/sifive_u.c  | 24 ++++--------------------
> hw/vfio/pci-quirks.c | 34 +++++++++-------------------------
> 2 files changed, 13 insertions(+), 45 deletions(-)
>

Ping

First round of trivial patches went already in for 7.1, hence a reminder.

Best regards,
Bernhard


  parent reply	other threads:[~2022-05-05 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 22:52 [PATCH RESEND 0/2] Resolve some redundant property accessors Bernhard Beschow
2022-03-01 22:52 ` [PATCH RESEND 1/2] hw/vfio/pci-quirks: Resolve redundant property getters Bernhard Beschow
2022-03-02 10:49   ` Bernhard Beschow
2022-03-21 10:57   ` Bernhard Beschow
2022-03-21 13:06     ` Philippe Mathieu-Daudé
2022-03-23 23:37       ` Bernhard Beschow
2022-03-01 22:52 ` [PATCH RESEND 2/2] hw/riscv/sifive_u: Resolve redundant property accessors Bernhard Beschow
2022-03-02  4:42   ` Alistair Francis
2022-05-05 16:52 ` Bernhard Beschow [this message]
2022-05-13 10:39   ` [PATCH RESEND 0/2] Resolve some " Bernhard Beschow
2022-05-17  3:41 ` Alistair Francis
2022-05-17 11:11   ` Bernhard Beschow

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=A987D65D-940B-4827-B547-92D27FBBA46E@gmail.com \
    --to=shentey@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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;
as well as URLs for NNTP newsgroup(s).