[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160701164656.GG4593@pd.tnic>
Date: Fri, 1 Jul 2016 18:46:56 +0200
From: Borislav Petkov <bp@...en8.de>
To: Andy Lutomirski <luto@...capital.net>
Cc: Michal Hocko <mhocko@...e.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>, Andi Kleen <ak@...ux.intel.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
X86 ML <x86@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dave Hansen <dave@...1.net>
Subject: Re: [PATCH 1/6] x86: fix duplicated X86_BUG(9) macro
On Fri, Jul 01, 2016 at 09:30:37AM -0700, Andy Lutomirski wrote:
> I put the ifdef there to prevent anyone from accidentally using it in
> a 64-bit code path, not to save a bit. We could put in the middle of
> the list to make the mistake much less likely to be repeated, I
> suppose.
Well, if someone does, someone will notice pretty soon, no?
I just don't see the reason to worry but maybe I'm missing it.
And we can call it X86_BUG_ESPFIX_X86_32 or so too...
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Powered by blists - more mailing lists