From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH] vfio/ccw: Replace warn_once_pfch() with warn_report_once()
Date: Mon, 24 Feb 2025 09:23:35 +0100 [thread overview]
Message-ID: <a9dbea52-0f90-4d5d-b8eb-6262a791ffea@redhat.com> (raw)
In-Reply-To: <20250214161936.1720039-1-clg@redhat.com>
On 2/14/25 17:19, Cédric Le Goater wrote:
> Use the common helper warn_report_once() instead of implementing its
> own.
>
> Cc: Eric Farman <farman@linux.ibm.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
> hw/vfio/ccw.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
I can update the trailers before sending a PR. For now, since it is
simple enough :
Applied to vfio-next.
Thanks,
C.
next prev parent reply other threads:[~2025-02-24 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 16:19 [PATCH] vfio/ccw: Replace warn_once_pfch() with warn_report_once() Cédric Le Goater
2025-02-24 8:23 ` Cédric Le Goater [this message]
2025-02-24 17:07 ` Eric Farman
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=a9dbea52-0f90-4d5d-b8eb-6262a791ffea@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=farman@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).