SUPERH platform development
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Joe Perches <joe@perches.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: Drop -Werror from kernel Makefile
Date: Sat, 10 Aug 2019 04:31:27 +0000	[thread overview]
Message-ID: <afceec12-e5eb-42b7-c67e-0dc5a23affdf@embeddedor.com> (raw)
In-Reply-To: <667995275e6a1cbcdaa93029c1b33e6b52fc6803.camel@perches.com>



On 8/9/19 11:20 PM, Joe Perches wrote:
> On Fri, 2019-08-09 at 21:47 -0500, Gustavo A. R. Silva wrote:
>> On 8/9/19 4:56 PM, Guenter Roeck wrote:
>>> On Fri, Aug 09, 2019 at 04:36:01PM -0500, Gustavo A. R. Silva wrote:
>>>> On 8/9/19 2:56 PM, Guenter Roeck wrote:
>>>>> On Sun, Aug 04, 2019 at 11:24:41PM -0400, Rich Felker wrote:
>>>>>> On Sun, Aug 04, 2019 at 07:14:23PM -0700, Guenter Roeck wrote:
>>>>>>> Since commit a035d552a93b ("Makefile: Globally enable fall-through
>>>>>>> warning"), all sh builds fail with errors such as
>>>>>>>
>>>>>>> arch/sh/kernel/disassemble.c: In function 'print_sh_insn':
>>>>>>> arch/sh/kernel/disassemble.c:478:8: error: this statement may fall through
>>>>>>>
>>>>>>> Since this effectively disables all build and boot tests for the
>>>>>>> architecture, let's drop -Werror from the sh kernel Makefile until
>>>>>>> the problems are fixed.
> []
>> On second thought it seems to me that this is not a good idea, at least
>> for mainline. For the time being I'll take this patch for linux-next only.
>>
>> Who is the maintainer of sh?
> 
> But whoever it may be, isn't particularly active.
> 
> MAINTAINERS-SUPERH
> MAINTAINERS-M:  Yoshinori Sato <ysato@users.sourceforge.jp>
> MAINTAINERS-M:  Rich Felker <dalias@libc.org>
> MAINTAINERS-L:  linux-sh@vger.kernel.org
> MAINTAINERS-Q:  http://patchwork.kernel.org/project/linux-sh/list/
> MAINTAINERS-S:  Maintained
> MAINTAINERS-F:  Documentation/sh/
> MAINTAINERS:F:  arch/sh/
> MAINTAINERS-F:  drivers/sh/
> 
>> The best solution is to fix those fall-through warnings you see. Could you
>> please send me all the warnings you see? I can try to fix them.
> 
> It's true it's a warning, but adding -Werror is rarely
> a good idea as gcc error output can change with every
> version.
> 

In the meantime I'll install sh4 and fix those warnings.

--
Gustavo

  reply	other threads:[~2019-08-10  4:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05  2:14 [PATCH] sh: Drop -Werror from kernel Makefile Guenter Roeck
2019-08-05  3:24 ` Rich Felker
2019-08-09 19:56   ` Guenter Roeck
2019-08-09 21:36     ` Gustavo A. R. Silva
2019-08-09 21:56       ` Guenter Roeck
2019-08-10  2:47         ` Gustavo A. R. Silva
2019-08-10  4:20           ` Joe Perches
2019-08-10  4:31             ` Gustavo A. R. Silva [this message]
2019-08-10  4:43               ` Gustavo A. R. Silva
2019-08-13  8:49 ` Yoshinori Sato
2019-08-13 13:18   ` Guenter Roeck
2019-08-15  0:59     ` Gustavo A. R. Silva
2019-08-15  3:14       ` Guenter Roeck

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=afceec12-e5eb-42b7-c67e-0dc5a23affdf@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