[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzN0B+ajX5ArsGYzqRMxDY26ptfTetSoYOOCVJKYHnZ7g@mail.gmail.com>
Date: Thu, 5 Apr 2018 14:20:05 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Martin Uecker <Martin.Uecker@....uni-goettingen.de>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Randy Dunlap <rdunlap@...radead.org>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Ingo Molnar <mingo@...nel.org>,
David Laight <David.Laight@...lab.com>,
Ian Abbott <abbotti@....co.uk>,
LKML <linux-kernel@...r.kernel.org>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH v7] kernel.h: Retain constant expression output for max()/min()
On Thu, Apr 5, 2018 at 1:42 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Ok, applied.
Ugh, during the merge window, we had actually grown a new example of
that "different enum types" problem:
struct drm_prop_enum_list enum_list[max(DRM_COLOR_ENCODING_MAX,
DRM_COLOR_RANGE_MAX)];
in drm_plane_create_color_properties() in the drm drm_color_mgmt.c file.
I ended up just fixing it up manually and added it to the commit. You
should double-check my change, I've pushed it out now that the build
seems ok for me.
There may be others hiding that weren't caught by my limited build
testing, trhough. So please keep an eye out for build warnings.
Linus
Powered by blists - more mailing lists