From: "tip-bot2 for Colin Ian King" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Colin Ian King <colin.king@canonical.com>,
Ingo Molnar <mingo@kernel.org>, Juergen Gross <jgross@suse.com>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/cleanups] x86/ioperm: Initialize pointer bitmap with NULL rather than 0
Date: Sun, 26 Jul 2020 17:58:45 -0000 [thread overview]
Message-ID: <159578632503.4006.1661941536167538433.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200721100217.407975-1-colin.king@canonical.com>
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 90fc73928fec2f62bbee1476781754c7392a7b61
Gitweb: https://git.kernel.org/tip/90fc73928fec2f62bbee1476781754c7392a7b61
Author: Colin Ian King <colin.king@canonical.com>
AuthorDate: Tue, 21 Jul 2020 11:02:17 +01:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Sun, 26 Jul 2020 19:52:55 +02:00
x86/ioperm: Initialize pointer bitmap with NULL rather than 0
The pointer bitmap is being initialized with a plain integer 0,
fix this by initializing it with a NULL instead.
Cleans up sparse warning:
arch/x86/xen/enlighten_pv.c:876:27: warning: Using plain integer
as NULL pointer
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Juergen Gross <jgross@suse.com>
Link: https://lore.kernel.org/r/20200721100217.407975-1-colin.king@canonical.com
---
arch/x86/xen/enlighten_pv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c
index c46b9f2..2aab43a 100644
--- a/arch/x86/xen/enlighten_pv.c
+++ b/arch/x86/xen/enlighten_pv.c
@@ -873,7 +873,7 @@ static void xen_load_sp0(unsigned long sp0)
static void xen_invalidate_io_bitmap(void)
{
struct physdev_set_iobitmap iobitmap = {
- .bitmap = 0,
+ .bitmap = NULL,
.nr_ports = 0,
};
prev parent reply other threads:[~2020-07-26 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 10:02 [PATCH][next] x86/ioperm: initialize " Colin King
2020-07-21 15:26 ` Jürgen Groß
2020-07-26 17:58 ` tip-bot2 for Colin Ian King [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=159578632503.4006.1661941536167538433.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=colin.king@canonical.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®