[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201909161516.A68C8239A@keescook>
Date: Mon, 16 Sep 2019 15:19:32 -0700
From: Kees Cook <keescook@...omium.org>
To: Joe Perches <joe@...ches.com>
Cc: hpa@...or.com, Peter Zijlstra <peterz@...radead.org>,
Pavel Machek <pavel@....cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Borislav Petkov <bp@...en8.de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"Gustavo A . R . Silva" <gustavo@...eddedor.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Kan Liang <kan.liang@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Jiri Olsa <jolsa@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Shawn Landden <shawn@....icu>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: treewide replacement of fallthrough comments with "fallthrough"
macro (was Re: [RFC PATCH] compiler_attributes.h: Add 'fallthrough' pseudo
keyword for switch/case use)
On Thu, Aug 15, 2019 at 11:15:53AM -0700, Kees Cook wrote:
> With that out of the way, yes, let's do a mass conversion. As mentioned
> before, I think "fallthrough;" should be used here (to match "break;").
> Let's fork the C language. :)
FWIW, last week I asked Linus at the maintainer's summit which he
preferred ("__fallthrough" or "fallthrough") and he said "fallthrough".
Joe, if you've still got the series ready, do you want to send it for
this merge window before -rc1 gets cut?
--
Kees Cook
Powered by blists - more mailing lists