From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Compiler Attributes for v5.9-rc4
Date: Sat, 5 Sep 2020 14:01:25 +0200 [thread overview]
Message-ID: <20200905120125.GA22011@gmail.com> (raw)
Hi Linus,
Luc requested me to pick a sparse fix on my queue, so here it goes
along with other two trivial Compiler Attributes ones (also from Luc).
Cheers,
Miguel
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
https://github.com/ojeda/linux.git tags/compiler-attributes-for-linus-v5.9-rc4
for you to fetch changes up to e5fc436f06eef54ef512ea55a9db8eb9f2e76959:
sparse: use static inline for __chk_{user,io}_ptr() (2020-08-29 09:29:32 +0200)
----------------------------------------------------------------
Two trivial changes and a fix for sparse:
- sparse: use static inline for __chk_{user,io}_ptr() (Luc Van Oostenryck)
- Compiler Attributes: fix comment concerning GCC 4.6 (Luc Van Oostenryck)
- Compiler Attributes: remove comment about sparse not supporting __has_attribute (Luc Van Oostenryck)
----------------------------------------------------------------
Luc Van Oostenryck (3):
Compiler Attributes: remove comment about sparse not supporting __has_attribute
Compiler Attributes: fix comment concerning GCC 4.6
sparse: use static inline for __chk_{user,io}_ptr()
include/linux/compiler_attributes.h | 8 +-------
include/linux/compiler_types.h | 4 ++--
2 files changed, 3 insertions(+), 9 deletions(-)
next reply other threads:[~2020-09-05 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 12:01 Miguel Ojeda [this message]
2020-09-05 22:36 ` [GIT PULL] Compiler Attributes for v5.9-rc4 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=20200905120125.GA22011@gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.