From: Paul Mackerras <paulus@ozlabs.org>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S HV: fix constant size warning
Date: Wed, 18 Jul 2018 06:29:27 +0000 [thread overview]
Message-ID: <20180718062927.GC27453@fergus> (raw)
In-Reply-To: <1530954445-6780-1-git-send-email-hofrat@osadl.org>
On Sat, Jul 07, 2018 at 11:07:25AM +0200, Nicholas Mc Guire wrote:
> The constants are 64bit but not explicitly declared UL resulting
> in sparse warnings. Fixed by declaring the constants UL.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
Thanks, patch applied to my kvm-ppc-next branch.
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@ozlabs.org>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Book3S HV: fix constant size warning
Date: Wed, 18 Jul 2018 16:29:27 +1000 [thread overview]
Message-ID: <20180718062927.GC27453@fergus> (raw)
In-Reply-To: <1530954445-6780-1-git-send-email-hofrat@osadl.org>
On Sat, Jul 07, 2018 at 11:07:25AM +0200, Nicholas Mc Guire wrote:
> The constants are 64bit but not explicitly declared UL resulting
> in sparse warnings. Fixed by declaring the constants UL.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
Thanks, patch applied to my kvm-ppc-next branch.
Paul.
next prev parent reply other threads:[~2018-07-18 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 9:07 [PATCH] KVM: PPC: Book3S HV: fix constant size warning Nicholas Mc Guire
2018-07-07 9:07 ` Nicholas Mc Guire
2018-07-18 6:29 ` Paul Mackerras [this message]
2018-07-18 6:29 ` Paul Mackerras
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=20180718062927.GC27453@fergus \
--to=paulus@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=hofrat@osadl.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.