From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Santosh Sivaraj <santosh@fossix.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] powerpc/kvm: Fall through switch case explicitly
Date: Mon, 29 Jul 2019 18:45:40 -0500 [thread overview]
Message-ID: <30ecba4e-a232-ad28-4c1a-5a173a7ac7cc@embeddedor.com> (raw)
In-Reply-To: <20190729181651.4b9586a7@canb.auug.org.au>
On 7/29/19 3:16 AM, Stephen Rothwell wrote:
> Hi Santosh,
>
> On Mon, 29 Jul 2019 11:25:36 +0530 Santosh Sivaraj <santosh@fossix.org> wrote:
>>
>> Implicit fallthrough warning was enabled globally which broke
>> the build. Make it explicit with a `fall through` comment.
>>
>> Signed-off-by: Santosh Sivaraj <santosh@fossix.org>
Reviewed-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Thanks!
--
Gustavo
>> ---
>> arch/powerpc/kvm/book3s_32_mmu.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/powerpc/kvm/book3s_32_mmu.c b/arch/powerpc/kvm/book3s_32_mmu.c
>> index 653936177857..18f244aad7aa 100644
>> --- a/arch/powerpc/kvm/book3s_32_mmu.c
>> +++ b/arch/powerpc/kvm/book3s_32_mmu.c
>> @@ -239,6 +239,7 @@ static int kvmppc_mmu_book3s_32_xlate_pte(struct kvm_vcpu *vcpu, gva_t eaddr,
>> case 2:
>> case 6:
>> pte->may_write = true;
>> + /* fall through */
>> case 3:
>> case 5:
>> case 7:
>> --
>> 2.20.1
>>
>
> Thanks
>
> Reviewed-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> This only shows up as a warning in a powerpc allyesconfig build.
>
next prev parent reply other threads:[~2019-07-29 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 5:55 [PATCH] powerpc/kvm: Fall through switch case explicitly Santosh Sivaraj
2019-07-29 8:16 ` Stephen Rothwell
2019-07-29 23:45 ` Gustavo A. R. Silva [this message]
2019-07-30 3:18 ` Stephen Rothwell
2019-07-30 3:30 ` Gustavo A. R. Silva
2019-07-30 3:50 ` Stephen Rothwell
2019-07-30 3:57 ` Gustavo A. R. Silva
2019-07-30 4:34 ` Stephen Rothwell
2019-07-30 22:50 ` Michael Ellerman
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=30ecba4e-a232-ad28-4c1a-5a173a7ac7cc@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=santosh@fossix.org \
--cc=sfr@canb.auug.org.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 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).