[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vd161xYcOgESiA2Ex5gzM39_CSSH11HsVzOyyA+g0rYTw@mail.gmail.com>
Date: Tue, 12 Feb 2019 12:19:53 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: Anders Roxell <anders.roxell@...aro.org>,
Mimi Zohar <zohar@...ux.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
linux-integrity <linux-integrity@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
linux-efi <linux-efi@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH 2/2] efi: fix build error redeclaration of enumerator
On Tue, Feb 12, 2019 at 12:16 PM Ard Biesheuvel
<ard.biesheuvel@...aro.org> wrote:
> On Tue, 12 Feb 2019 at 11:09, Anders Roxell <anders.roxell@...aro.org> wrote:
> >
> > Commit a893ea15d764 ("tpm: move tpm_chip definition to
> > include/linux/tpm.h") introduced a build error when both ima and efi is
> > enabled. What happens is that both headers (ima.h and efi.h) defines the
> > same 'NONE' constant, and it broke when they started getting included
> > from the same file.
> I'd argue that we should apply both patches. 'NONE' is far too
> generic, so it requires a subsystem prefix if it has a special meaning
> inside a subsystem.
I was about to say the same thing.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists