From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Guenter Roeck <linux@roeck-us.net>, Rich Felker <dalias@libc.org>
Cc: 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: Fri, 9 Aug 2019 16:36:01 -0500 [thread overview]
Message-ID: <5f26547f-b48e-4b9f-b8ef-858283915e3d@embeddedor.com> (raw)
In-Reply-To: <20190809195630.GA15606@roeck-us.net>
Hi Guenter,
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.
>>>
>>> Cc: Gustavo A. R. Silva <gustavo@embeddedor.com>
>>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>>
>> Acked-by: Rich Felker <dalias@libc.org>
>>
> Any chance to get this or a similar patch applied soon ? All sh builds
> in mainline and -next are still broken.
>
If no one cares, I can add it to my tree and include it in my pull-request
for 5.3-rc4.
I would just need your Tested-by.
Thanks
--
Gustavo
> Thanks,
> Guenter
>
>>> ---
>>> arch/sh/kernel/Makefile | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> diff --git a/arch/sh/kernel/Makefile b/arch/sh/kernel/Makefile
>>> index 59673f8a3379..ef65f0625c6c 100644
>>> --- a/arch/sh/kernel/Makefile
>>> +++ b/arch/sh/kernel/Makefile
>>> @@ -47,5 +47,3 @@ obj-$(CONFIG_DWARF_UNWINDER) += dwarf.o
>>> obj-$(CONFIG_PERF_EVENTS) += perf_event.o perf_callchain.o
>>> obj-$(CONFIG_DMA_NONCOHERENT) += dma-coherent.o
>>> obj-$(CONFIG_HAVE_HW_BREAKPOINT) += hw_breakpoint.o
>>> -
>>> -ccflags-y := -Werror
>>> --
>>> 2.7.4
next prev parent reply other threads:[~2019-08-09 21:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 2:14 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 [this message]
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
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=5f26547f-b48e-4b9f-b8ef-858283915e3d@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=dalias@libc.org \
--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
all inboxes | Powered by JetHome®