From: John Hubbard <jhubbard@nvidia.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Thomas Gleixner <tglx@linutronix.de>
Cc: <john.hubbard@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] x86/boot: clear some fields explicitly
Date: Thu, 25 Jul 2019 13:44:50 -0700 [thread overview]
Message-ID: <06cbabb1-d3bc-5ed5-8cbe-bee361bb3c5b@nvidia.com> (raw)
In-Reply-To: <3831bbff-631a-2e62-9e82-e2b6181421c8@zytor.com>
On 7/25/19 1:38 PM, H. Peter Anvin wrote:
> On 7/25/19 12:22 AM, Thomas Gleixner wrote:
> The easy way would be to put in a suitable cast to clear the warning -- I
> would not be surprised if an explicit cast to something like (void *) would
> quiet the warning, or else (yuck) put in an explicit (well-commented) #pragma
> to shut it up.
>
I wish. The first thing I tried was a (void*) cast, and the second thing
was declaring a void pointer instead. But the new compiler is fiendishly
clever, and figured me out in both cases.
The #pragma I haven't tried, it seems like a bit too far.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2019-07-25 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 23:15 [PATCH 0/1] x86/boot: clear some fields explicitly john.hubbard
2019-07-24 23:15 ` [PATCH 1/1] " john.hubbard
2019-07-25 2:12 ` hpa
2019-07-25 6:49 ` John Hubbard
2019-07-25 7:22 ` Thomas Gleixner
2019-07-25 20:33 ` John Hubbard
2019-07-25 21:48 ` Thomas Gleixner
2019-07-25 21:57 ` hpa
2019-07-25 22:03 ` Thomas Gleixner
2019-07-25 22:28 ` H. Peter Anvin
2019-07-25 22:37 ` Thomas Gleixner
2019-07-26 0:36 ` John Hubbard
2019-07-25 22:42 ` John Hubbard
2019-07-26 7:43 ` Thomas Gleixner
2019-07-25 20:38 ` H. Peter Anvin
2019-07-25 20:44 ` John Hubbard [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=06cbabb1-d3bc-5ed5-8cbe-bee361bb3c5b@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).