From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Samuel Tardieu" <sam@rfc1149.net>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"open list:STM32L4x5 SoC Family" <qemu-arm@nongnu.org>
Subject: Re: [PATCH] hw/char/stm32l4x5_usart: Accept character input upon RDR read
Date: Tue, 08 Sep 2026 17:30:42 +0100 [thread overview]
Message-ID: <87y0dbaeod.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA_hbEUYO+0vSDZDGtyp8uo+The9q_Bkry2WwJY40EVvTQ@mail.gmail.com> (Peter Maydell's message of "Tue, 8 Sep 2026 16:51:11 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Wed, 2 Sept 2026 at 18:00, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> Looking through existing serial devices this seems to be a common
>> pattern so it makes sense to me this is the right fix and matches the
>> API description.
>>
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/4389
>> Reported-by: Jan Brittenson (@bson)
>> Suggested-by: Jan Brittenson (@bson)
>> AI-used-for: fetch issue, apply proposed patch, verify build and qtests
>
> I think the fix is fine, but given this tag I'm not sure what
> you want me to do with this.
well in this case the AI never wrote any code, it just applied the fix
from the issue and tested it which I think is within the current policy.
>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> -- PMM
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-09-08 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:59 [PATCH] hw/char/stm32l4x5_usart: Accept character input upon RDR read Alex Bennée
2026-09-08 15:51 ` Peter Maydell
2026-09-08 16:30 ` Alex Bennée [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=87y0dbaeod.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sam@rfc1149.net \
/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