From: Paolo Bonzini <pbonzini@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] scripts/update-linux-headers.sh: adjust for Linux 4.21-rc1 (or 5.0-rc1)
Date: Fri, 4 Jan 2019 12:02:37 +0100 [thread overview]
Message-ID: <c60f6b8a-810a-cf50-aafd-8ca3991e23c2@redhat.com> (raw)
In-Reply-To: <20190104102655.3bf599f5.cohuck@redhat.com>
On 04/01/19 10:26, Cornelia Huck wrote:
> On Fri, 4 Jan 2019 09:27:30 +0100
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>> There are three new indirect inclusions: vhost_types.h, which we'll
>> shortly put to use as a portable header and thus is copied to
>> standard-headers; and new per-subtarget versions of MIPS unistd.h
>> and PowerPC unistd.h.
>>
>> Because vhost.h includes vhost_types.h, we also need a proxy include
>> from linux/vhost.h to standard-headers.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> scripts/update-linux-headers.sh | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>
> I still think we could squash this change (and the description :) with
> the headers update, but I don't object to a separate change, either.
Me too, but I figured I'd rather not pull another tantrum like I did for
multiline comments...
Paolo
next prev parent reply other threads:[~2019-01-04 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 8:27 [Qemu-devel] [PATCH 0/2] include: update Linux headers to 4.21-rc1/5.0-rc1 Paolo Bonzini
2019-01-04 8:27 ` [Qemu-devel] [PATCH 1/2] scripts/update-linux-headers.sh: adjust for Linux 4.21-rc1 (or 5.0-rc1) Paolo Bonzini
2019-01-04 9:26 ` Cornelia Huck
2019-01-04 11:02 ` Paolo Bonzini [this message]
2019-01-04 11:58 ` Peter Maydell
2019-01-04 14:17 ` Aleksandar Markovic
2019-01-04 8:27 ` [Qemu-devel] [PATCH 2/2] include: update Linux headers to 4.21-rc1/5.0-rc1 Paolo Bonzini
2019-01-04 9:27 ` Cornelia Huck
2019-01-04 15:18 ` [Qemu-devel] [PATCH 0/2] " Michael S. Tsirkin
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=c60f6b8a-810a-cf50-aafd-8ca3991e23c2@redhat.com \
--to=pbonzini@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).