From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Joe Perches <joe@perches.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] sh: kernel: disassemble: Mark expected switch fall-throughs
Date: Sat, 10 Aug 2019 05:14:02 +0000 [thread overview]
Message-ID: <9f8dd34d-373c-eaf9-00ec-436745a1a025@embeddedor.com> (raw)
In-Reply-To: <996bc110024500842a627ea75cb43b7cd00ef36c.camel@perches.com>
On 8/10/19 12:08 AM, Joe Perches wrote:
> On Sat, 2019-08-10 at 00:01 -0500, Gustavo A. R. Silva wrote:
>> Mark switch cases where we are expecting to fall through.
>>
>> Fix the following warnings (Building: defconfig sh):
> []
>> diff --git a/arch/sh/kernel/disassemble.c b/arch/sh/kernel/disassemble.c
> []
>> @@ -477,6 +477,7 @@ static void print_sh_insn(u32 memaddr, u16 insn)
>> case FD_REG_N:
>> if (0)
>> goto d_reg_n;
>
> Might as well remove this if (0) goto,
> remove the added comment
>
You're right. I'll respin and stop working this Friday midnight.
>> + /* else, fall through */
>> case F_REG_N:
>> printk("fr%d", rn);
>> break;
>> @@ -488,6 +489,7 @@ static void print_sh_insn(u32 memaddr, u16 insn)
>> printk("xd%d", rn & ~1);
>> break;
>> }
>> + /* else, fall through */
>> d_reg_n:
>
> and remove this only use of d_reg_n
>
Sure.
Thanks
--
Gustavo
>> case D_REG_N:
>> printk("dr%d", rn);
>> @@ -497,6 +499,7 @@ static void print_sh_insn(u32 memaddr, u16 insn)
>> printk("xd%d", rm & ~1);
>> break;
>> }
>> + /* else, fall through */
>> case D_REG_M:
>> printk("dr%d", rm);
>> break;
>
prev parent reply other threads:[~2019-08-10 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 5:01 [PATCH] sh: kernel: disassemble: Mark expected switch fall-throughs Gustavo A. R. Silva
2019-08-10 5:08 ` Joe Perches
2019-08-10 5:14 ` Gustavo A. R. Silva [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=9f8dd34d-373c-eaf9-00ec-436745a1a025@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=dalias@libc.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ysato@users.sourceforge.jp \
/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