From: Eric Farman <farman@linux.ibm.com>
To: Peter Xu <peterx@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v3 1/3] update-linux-headers: Include const.h
Date: Thu, 7 Jan 2021 11:51:27 -0500 [thread overview]
Message-ID: <9fcc99ca-aa60-2249-dfc5-bf0018b3ddb0@linux.ibm.com> (raw)
In-Reply-To: <20210106190345.GJ149908@xz-x1>
On 1/6/21 2:03 PM, Peter Xu wrote:
> On Mon, Jan 04, 2021 at 09:20:55PM +0100, Eric Farman wrote:
>> Kernel commit a85cbe6159ff ("uapi: move constants from
>> <linux/kernel.h> to <linux/const.h>") breaks our script
>> because of the unrecognized include. Let's add that to
>> our processing.
>>
>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>> ---
>> scripts/update-linux-headers.sh | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
>> index 9efbaf2f84..fa6f2b6272 100755
>> --- a/scripts/update-linux-headers.sh
>> +++ b/scripts/update-linux-headers.sh
>> @@ -41,6 +41,7 @@ cp_portable() {
>> -e 'pvrdma_verbs' \
>> -e 'drm.h' \
>> -e 'limits' \
>> + -e 'linux/const' \
>> -e 'linux/kernel' \
>> -e 'linux/sysinfo' \
>> -e 'asm-generic/kvm_para' \
>> @@ -190,7 +191,9 @@ for i in "$tmpdir"/include/linux/*virtio*.h \
>> "$tmpdir/include/linux/input.h" \
>> "$tmpdir/include/linux/input-event-codes.h" \
>> "$tmpdir/include/linux/pci_regs.h" \
>> - "$tmpdir/include/linux/ethtool.h" "$tmpdir/include/linux/kernel.h" \
>> + "$tmpdir/include/linux/ethtool.h" \
>> + "$tmpdir/include/linux/const.h" \
>> + "$tmpdir/include/linux/kernel.h" \
>> "$tmpdir/include/linux/vhost_types.h" \
>> "$tmpdir/include/linux/sysinfo.h"; do
>> cp_portable "$i" "$output/include/standard-headers/linux"
>> --
>> 2.17.1
>
> So I think I came to the same change when trying to update the headers. :)
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
Thank you! :)
>
> Could I ask why the const.h is installed into include/standard-headers/linux
> rather than linux-headers/linux? When I was working on my version I failed to
> figure out the difference.
Considering the main difference is whether the header file is copied
directly or edited with a bunch of substitutions, and const.h doesn't
get modified by those substitutions, I suppose it could go in
linux-headers itself. But I opted to just keep it near its friends
(ethtool.h and kernel.h both include const.h, and end up including
if_ether.h, sysinfo.h, and types.h) in include/standard-headers.
>
> One answer is ethtool.h is there which included const.h, but I guess that's not
> the real one.
>
> Thanks,
>
next prev parent reply other threads:[~2021-01-07 16:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:20 [PATCH v3 0/3] vfio-ccw: Implement request notifier Eric Farman
2021-01-04 20:20 ` [PATCH v3 1/3] update-linux-headers: Include const.h Eric Farman
2021-01-06 19:03 ` Peter Xu
2021-01-07 16:51 ` Eric Farman [this message]
2021-01-07 17:05 ` Peter Maydell
2021-01-07 17:50 ` Eric Farman
2021-01-07 19:12 ` Peter Xu
2021-01-07 6:52 ` Philippe Mathieu-Daudé
2021-01-04 20:20 ` [PATCH v3 2/3] Update linux headers to 5.11-rc2 Eric Farman
2021-01-11 12:54 ` Cornelia Huck
2021-01-11 13:00 ` Michael S. Tsirkin
2021-01-11 13:43 ` Cornelia Huck
2021-01-11 15:00 ` Michael S. Tsirkin
2021-01-11 15:11 ` Eric Farman
2021-01-11 15:18 ` Michael S. Tsirkin
2021-01-11 16:05 ` Cornelia Huck
2021-01-13 11:27 ` Cornelia Huck
2021-01-04 20:20 ` [PATCH v3 3/3] vfio-ccw: Connect the device request notifier Eric Farman
2021-01-13 12:58 ` [PATCH v3 0/3] vfio-ccw: Implement " Cornelia Huck
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=9fcc99ca-aa60-2249-dfc5-bf0018b3ddb0@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--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 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).