From: Peter Maydell <peter.maydell@linaro.org>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 0/2] chardev patches
Date: Mon, 2 Dec 2024 16:15:59 +0000 [thread overview]
Message-ID: <CAFEAcA-pyPpNOphihm81OyfoSpKCOpXmtm_WgVha=EvZYvBsGw@mail.gmail.com> (raw)
In-Reply-To: <20241202122709.100177-1-marcandre.lureau@redhat.com>
On Mon, 2 Dec 2024 at 12:27, <marcandre.lureau@redhat.com> wrote:
>
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> The following changes since commit 72b88908d12ee9347d13539c7dd9a252625158d1:
>
> Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2024-11-29 10:09:05 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/marcandre.lureau/qemu.git tags/chr-pull-request
>
> for you to fetch changes up to e6214fd6d48e704ed3aed6ea2053a9756d0ca13f:
>
> chardev/char-mux: make boolean bit check instead of find_next_bit() (2024-12-02 16:23:12 +0400)
>
> ----------------------------------------------------------------
> chardev patch queue
>
> ----------------------------------------------------------------
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/9.2
for any user-visible changes.
-- PMM
next prev parent reply other threads:[~2024-12-02 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 12:27 [PULL 0/2] chardev patches marcandre.lureau
2024-12-02 12:27 ` [PULL 1/2] chardev/char-mux: shift unsigned long to avoid 32-bit overflow marcandre.lureau
2024-12-02 12:27 ` [PULL 2/2] chardev/char-mux: make boolean bit check instead of find_next_bit() marcandre.lureau
2024-12-02 16:15 ` Peter Maydell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 13:39 [PULL 0/2] chardev patches marcandre.lureau
2024-12-03 16:50 ` Peter Maydell
2024-10-09 8:39 marcandre.lureau
2024-10-09 19:11 ` Peter Maydell
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='CAFEAcA-pyPpNOphihm81OyfoSpKCOpXmtm_WgVha=EvZYvBsGw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).