[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nCa=TQvpgcOcLceGTDc+7KxPmD4NCMamqAqV2o5au89A@mail.gmail.com>
Date: Fri, 14 Dec 2018 11:02:40 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: liuxiaozhou@...edance.com, Greg KH <gregkh@...uxfoundation.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
Paul Burton <paul.burton@...s.com>,
Arnd Bergmann <arnd@...db.de>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH v2] Compiler Attributes: don't pollute userspace with
macro definitions
On Thu, Dec 13, 2018 at 11:25 PM Nick Desaulniers
<ndesaulniers@...gle.com> wrote:
>
> Moving the __KERNEL__ guard should not affect the kernel, only what
> userspace sees. __gnu_inline only affects which
> implementation/definition you get, so even if userspace doesn't know
> what the kernel's inline is redefined to, it should not matter as
> userspace should only ever care about the function signature, which
> does not change between our definitions of inline.
Hm... I am unsure what you mean by this. Were you replying to me or to
the original patch?
Cheers,
Miguel
Powered by blists - more mailing lists