From: Markus Armbruster <armbru@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
marcandre.lureau@redhat.com, berrange@redhat.com,
thuth@redhat.com, philmd@linaro.org, bcain@quicinc.com,
imp@bsdimp.com, stefanha@redhat.com
Subject: Re: [PATCH 0/1] Enable -Wshadow=local
Date: Fri, 27 Oct 2023 06:41:52 +0200 [thread overview]
Message-ID: <878r7o7k33.fsf@pond.sub.org> (raw)
In-Reply-To: <CAJSP0QW2uVv1s6JnNFj5HC13vO=yGsGB0wb_mRJvUQXoeCLvQA@mail.gmail.com> (Stefan Hajnoczi's message of "Fri, 27 Oct 2023 09:52:24 +0900")
Stefan Hajnoczi <stefanha@gmail.com> writes:
> On Thu, 26 Oct 2023 at 14:32, Markus Armbruster <armbru@redhat.com> wrote:
>>
>> Requires Brian's pull request and two patches from Thomas to compile:
>>
>> [PULL 0/2] hex queue - GETPC() fixes, shadowing fixes
>> [PATCH v2] block/snapshot: Fix compiler warning with -Wshadow=local
>> [PATCH v2] migration/ram: Fix compilation with -Wshadow=local
>>
>> Stefan, the PR was posted a week ago; anything blocking it?
>
> It's not in a pull request, so I won't see it. I don't have tooling
> that can spot individual patch series that need to go into
> qemu.git/master, so I rely on being emailed about them.
I'm inquiring about this one:
https://lore.kernel.org/qemu-devel/20231019021733.2258592-1-bcain@quicinc.com/
Looks like a PR to me.
> Would you like me to merge this patch series into qemu.git/master?
Yes, I'd like you merge Brian's PR I linked to.
[...]
next prev parent reply other threads:[~2023-10-27 4:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 5:31 [PATCH 0/1] Enable -Wshadow=local Markus Armbruster
2023-10-26 5:31 ` [PATCH 1/1] meson: " Markus Armbruster
2023-10-26 5:44 ` Thomas Huth
2023-10-26 5:51 ` Warner Losh
2023-10-26 5:55 ` Thomas Huth
2023-10-26 5:58 ` Philippe Mathieu-Daudé
2023-10-26 6:12 ` Thomas Huth
2023-10-26 6:17 ` Philippe Mathieu-Daudé
2023-10-26 6:50 ` Markus Armbruster
2023-10-26 10:05 ` Daniel P. Berrangé
2023-10-26 5:54 ` [PATCH 0/1] " Warner Losh
2023-10-27 0:52 ` Stefan Hajnoczi
2023-10-27 2:25 ` Brian Cain
2023-10-27 4:41 ` Markus Armbruster [this message]
2023-10-30 4:58 ` Stefan Hajnoczi
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=878r7o7k33.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=bcain@quicinc.com \
--cc=berrange@redhat.com \
--cc=imp@bsdimp.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.