From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PULL 0/2] Update linux-headers to v5.18-rc6
Date: Thu, 12 May 2022 16:01:45 +0200 [thread overview]
Message-ID: <8812e17d-d1fb-1553-06c2-5394123f995b@redhat.com> (raw)
In-Reply-To: <20220512102942.1134141-1-thuth@redhat.com>
On 12/05/2022 12.29, Thomas Huth wrote:
> Hi!
>
> The following changes since commit ec11dc41eec5142b4776db1296972c6323ba5847:
>
> Merge tag 'pull-misc-2022-05-11' of git://repo.or.cz/qemu/armbru into staging (2022-05-11 09:00:26 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/thuth/qemu.git tags/pull-request-2022-05-12
>
> for you to fetch changes up to 98cdec27e4396a2982c85ed148f70770bb6600b4:
>
> vfio: tolerate migration protocol v1 uapi renames (2022-05-12 11:00:05 +0200)
>
> ----------------------------------------------------------------
> * Update the linux headers to v5.18-rc6 (required for multiple patch
> series that are currently in flight)
> * Fix the vfio code to compile again after the header update
>
> I'm sending this as a separate pull request, so that the the patch
> series that are currently in flight do not have to deal each time
> with the ugly vfio macro rename anymore.
Replying to the 0/2 header to make sure that this gets seen before it gets
merged: Please don't merge this series, as Avihai noticed correctly, this
needs more work first.
Thomas
prev parent reply other threads:[~2022-05-12 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 10:29 [PULL 0/2] Update linux-headers to v5.18-rc6 Thomas Huth
2022-05-12 10:29 ` [PULL 1/2] linux-headers: Update headers " Thomas Huth
2022-05-12 10:29 ` [PULL 2/2] vfio: tolerate migration protocol v1 uapi renames Thomas Huth
2022-05-12 13:53 ` Avihai Horon
2022-05-12 14:04 ` Thomas Huth
2022-05-12 14:01 ` Thomas Huth [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=8812e17d-d1fb-1553-06c2-5394123f995b@redhat.com \
--to=thuth@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).