From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ALOK JHA <alok08jha@gmail.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Kees Cook <keescook@chromium.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Makefile: Globally enable fall-through warning
Date: Tue, 17 May 2022 14:59:12 -0500 [thread overview]
Message-ID: <20220517195912.GA10952@embeddedor> (raw)
In-Reply-To: <20220517114601.55016e298905d6b6aa0fa873@linux-foundation.org>
On Tue, May 17, 2022 at 11:46:01AM -0700, Andrew Morton wrote:
> On Tue, 17 May 2022 23:05:34 +0530 ALOK JHA <alok08jha@gmail.com> wrote:
>
> > From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
> >
> > Now that all the fall-through warnings have been addressed in the
> > kernel, enable the fall-through warning globally.
> >
> > Also, update the deprecated.rst file to include implicit fall-through
> > as 'deprecated' so people can be pointed to a single location for
> > justification.
> >
> > ...
> >
> > --- a/Documentation/process/deprecated.rst
> > +++ b/Documentation/process/deprecated.rst
> > @@ -119,3 +119,17 @@ array may exceed the remaining memory in the stack segment. This could
> > lead to a crash, possible overwriting sensitive contents at the end of the
> > stack (when built without `CONFIG_THREAD_INFO_IN_TASK=y`), or overwriting
> > memory adjacent to the stack (when built without `CONFIG_VMAP_STACK=y`)
> > +
> > +Implicit switch case fall-through
> > +---------------------------------
> >
> > ...
> >
>
> Documentation/process/deprecated.rst already has a section "Implicit
> switch case fall-through". Maybe you're working against an old kernel.
> Please update when resending.
This looks like spam to me.
Let's just ignore this.
--
Gustavo
next prev parent reply other threads:[~2022-05-17 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 17:35 [PATCH] Makefile: Globally enable fall-through warning ALOK JHA
2022-05-17 18:42 ` Andrew Morton
2022-05-17 18:46 ` Andrew Morton
2022-05-17 19:40 ` Jeff Johnson
2022-05-17 19:59 ` Gustavo A. R. Silva [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-05 17:14 Omar el Azouny
2025-05-05 17:53 ` Miguel Ojeda
2026-01-10 1:34 MIshraMohit21-LE
2026-01-10 3:12 ` Gustavo A. R. Silva
[not found] ` <CAP5HdgoFya1NfeJH0wT7KtzqaFmupn5C-kSwXNEtEdbq5bQSEw@mail.gmail.com>
2026-01-10 4:04 ` Gustavo A. R. Silva
2026-01-22 15:53 Simone Rea
2026-01-22 18:19 ` Randy Dunlap
2026-01-22 18:44 ` Andrew Morton
2026-01-22 18:46 ` Randy Dunlap
2026-01-22 22:35 ` Miguel Ojeda
[not found] ` <CAEfWggNK7DgsRHXTE8BhWCTuDKyt6pMR_9UEHEs1NKPfPPyopw@mail.gmail.com>
2026-01-23 1:51 ` Gustavo A. R. Silva
[not found] <20260131054051.6938-1-david@stennet.com>
2026-01-31 5:40 ` david
2026-01-31 5:33 ` Gustavo A. R. Silva
2026-02-14 9:19 Rishabh
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=20220517195912.GA10952@embeddedor \
--to=gustavoars@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alok08jha@gmail.com \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/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