linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Xiaozhou Liu <liuxiaozhou@bytedance.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [GIT PULL] compiler-attributes for v4.20
Date: Fri, 21 Dec 2018 22:29:22 +0100	[thread overview]
Message-ID: <20181221212922.GA14646@gmail.com> (raw)

Hi Linus,

I picked this one up even if it is not exactly compiler-attributes.

I would like if you can take a look at the patch, please. The patch is harmless
for the kernel, but v4.19 was released with a few macros exposed to userspace
as the patch explains; which this removes, so it *could* happen that we break
something for someone (although leaving inline redefined is probably worse).

Greg said he would want to pick this if this ends up in your tree.

The patch has been in linux-next for a few days.

Cheers,
Miguel

The following changes since commit 40e020c129cfc991e8ab4736d2665351ffd1468d:

  Linux 4.20-rc6 (2018-12-09 15:31:00 -0800)

are available in the Git repository at:

  https://github.com/ojeda/linux.git tags/compiler-attributes-for-linus-v4.20

for you to fetch changes up to 71391bdd2e9aab188f86bf1ecd9b232531ec7eea:

  include/linux/compiler_types.h: don't pollute userspace with macro definitions (2018-12-14 16:57:16 +0100)

----------------------------------------------------------------
A cleanup for userspace in compiler_types.h

  - don't pollute userspace with macro definitions
    From Xiaozhou Liu

----------------------------------------------------------------
Xiaozhou Liu (1):
      include/linux/compiler_types.h: don't pollute userspace with macro definitions

 include/linux/compiler_types.h | 108 ++++++++++++++++++++---------------------
 1 file changed, 54 insertions(+), 54 deletions(-)

             reply	other threads:[~2018-12-21 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 21:29 Miguel Ojeda [this message]
2018-12-22 23:10 ` [GIT PULL] compiler-attributes for v4.20 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181221212922.GA14646@gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuxiaozhou@bytedance.com \
    --cc=ndesaulniers@google.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).