From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Sean Christopherson <seanjc@google.com>,
David Woodhouse <dwmw2@infradead.org>,
Alexander Graf <graf@amazon.de>
Subject: [kvm-unit-tests PATCH 1/7] bitops: Include stdbool.h and stddef.h as necessary
Date: Thu, 20 Jan 2022 00:29:17 +0000 [thread overview]
Message-ID: <20220120002923.668708-2-seanjc@google.com> (raw)
In-Reply-To: <20220120002923.668708-1-seanjc@google.com>
Include stdbool.h and stddef.h in bitops.h to pick up the definitions for
"bool" and "size_t" respectively.
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
lib/bitops.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/bitops.h b/lib/bitops.h
index 308aa865..81a06a47 100644
--- a/lib/bitops.h
+++ b/lib/bitops.h
@@ -1,6 +1,9 @@
#ifndef _BITOPS_H_
#define _BITOPS_H_
+#include <stdbool.h>
+#include <stddef.h>
+
/*
* Adapted from
* include/linux/bitops.h
--
2.34.1.703.g22d0c6ccf7-goog
next prev parent reply other threads:[~2022-01-20 0:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 0:29 [kvm-unit-tests PATCH 0/7] x86/debug: More single-step #DB tests Sean Christopherson
2022-01-20 0:29 ` Sean Christopherson [this message]
2022-01-20 0:29 ` [kvm-unit-tests PATCH 2/7] x86/debug: Add framework for " Sean Christopherson
2022-01-20 0:29 ` [kvm-unit-tests PATCH 3/7] x86/debug: Test OUT instead of RDMSR for single-step #DB emulation test Sean Christopherson
2022-01-24 14:15 ` Paolo Bonzini
2022-01-20 0:29 ` [kvm-unit-tests PATCH 4/7] x86/debug: Run single-step #DB tests in usermode (and kernel mode) Sean Christopherson
2022-01-20 0:29 ` [kvm-unit-tests PATCH 5/7] x86: Overhaul definitions for DR6 and DR7 bits Sean Christopherson
2022-01-20 0:29 ` [kvm-unit-tests PATCH 6/7] x86/debug: Add single-step #DB + STI/MOVSS blocking tests Sean Christopherson
2022-01-20 0:29 ` [kvm-unit-tests PATCH 7/7] x86/debug: Explicitly write DR6 in the H/W watchpoint + DR6.BS sub-test Sean Christopherson
2022-01-20 0:47 ` Jim Mattson
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=20220120002923.668708-2-seanjc@google.com \
--to=seanjc@google.com \
--cc=dwmw2@infradead.org \
--cc=graf@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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).