[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <623eb1bc61951ed3c68a9224b9aa99a25e763913.camel@perches.com>
Date: Tue, 17 Mar 2020 15:13:29 -0700
From: Joe Perches <joe@...ches.com>
To: Daniel Vetter <daniel@...ll.ch>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] drm: drm_vm: Use fallthrough;
On Tue, 2020-03-17 at 17:48 +0100, Daniel Vetter wrote:
> On Thu, Mar 12, 2020 at 12:17:12PM -0700, Joe Perches wrote:
> > Convert /* fallthrough */ style comments to fallthrough;
> >
> > Convert the various uses of fallthrough comments to fallthrough;
> >
> > Done via script
> > Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe@perches.com/
> >
> > And by hand:
> >
> > This file has a fallthrough comment outside of an #ifdef block
> > that causes gcc to emit a warning if converted in-place.
> >
> > So move the new fallthrough; inside the containing #ifdef/#endif too.
> >
> > Signed-off-by: Joe Perches <joe@...ches.com>
>
> Acked-by: Daniel Vetter <daniel.vetter@...ll.ch>
>
> I'm assuming this all lands through a special pull? Or should I apply
> this?
Hi Daniel.
I think you should apply this.
The idea here is to allow a scripted conversion at some
point and this patch is necessary to avoid new compiler
warnings after running the script.
Powered by blists - more mailing lists