qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: lvivier@redhat.com, peter.maydell@linaro.org, thuth@redhat.com,
	Gavin Shan <gwshan@linux.vnet.ibm.com>,
	qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH v8 1/7] scripts: Allow include "stdint.h" in virtio headers
Date: Mon, 14 Sep 2015 11:36:09 +1000	[thread overview]
Message-ID: <1442194575-8537-2-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
In-Reply-To: <1442194575-8537-1-git-send-email-gwshan@linux.vnet.ibm.com>

This allows to include "stdint.h" in virtio header files. Otherwise,
scripts/update-linux-headers.sh fails when updating headers from
Linux 4.2.rc8 kernel. include/uapi/linux/virtio_ring.h starts to
include "stdint.h" from commit d768f32a ("virtio: Fix typecast of
pointer in vring_init()").

Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
---
 scripts/update-linux-headers.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/scripts/update-linux-headers.sh b/scripts/update-linux-headers.sh
index f0e830c..2fddf2e 100755
--- a/scripts/update-linux-headers.sh
+++ b/scripts/update-linux-headers.sh
@@ -37,7 +37,8 @@ cp_virtio() {
         mkdir -p "$to"
         for f in $virtio; do
             if
-                grep '#include' "$f" | grep -v -e 'linux/virtio' \
+                grep '#include' "$f" | grep -v -e 'stdint' \
+                                             -e 'linux/virtio' \
                                              -e 'linux/types' \
                                              -e 'linux/if_ether' \
                                              -e 'sys/' \
-- 
2.1.0

  reply	other threads:[~2015-09-14  1:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  1:36 [Qemu-devel] [PATCH v8 0/7] sPAPR: Support EEH Error Injection Gavin Shan
2015-09-14  1:36 ` Gavin Shan [this message]
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 2/7] scripts: Include arch/powerpc/include/uapi/asm/eeh.h Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 3/7] scripts: Submit changes while updating linux headers Gavin Shan
2015-09-14  4:12   ` David Gibson
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 4/7] Synchronize Linux headers from kernel 4.3.0-rc1 Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 5/7] Obsolete PCI_MSIX_FLAGS_BIRMASK Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 6/7] sPAPR: Support RTAS call ibm, {open, close}-errinjct Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 7/7] sPAPR: Support RTAS call ibm,errinjct Gavin Shan
2015-09-14  4:14 ` [Qemu-devel] [PATCH v8 0/7] sPAPR: Support EEH Error Injection David Gibson
2015-09-15  6:03   ` Thomas Huth
2015-10-01  7:25     ` Gavin Shan

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=1442194575-8537-2-git-send-email-gwshan@linux.vnet.ibm.com \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).