From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Matt Evans" <mev@rivosinc.com>
Subject: [GIT PULL] asm-generic fixes for 6.3
Date: Thu, 06 Apr 2023 10:12:53 +0200 [thread overview]
Message-ID: <f44680f5-df08-4034-9ed7-6d43ee4c4c2a@app.fastmail.com> (raw)
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git tags/asm-generic-fixes-6.3
for you to fetch changes up to 656e9007ef5862746cdf7ac16267c8e06e7b0989:
asm-generic: avoid __generic_cmpxchg_local warnings (2023-04-04 17:58:11 +0200)
----------------------------------------------------------------
asm-generic fixes for 6.3
These are minor fixes to address false-positive build warnings:
Some of the less common I/O accessors are missing __force casts and
cause sparse warnings for their implied byteswap, and a recent change
to __generic_cmpxchg_local() causes a warning about constant integer
truncation.
----------------------------------------------------------------
Arnd Bergmann (1):
asm-generic: avoid __generic_cmpxchg_local warnings
Vladimir Oltean (2):
asm-generic/io.h: suppress endianness warnings for readq() and writeq()
asm-generic/io.h: suppress endianness warnings for relaxed accessors
include/asm-generic/atomic.h | 4 ++--
include/asm-generic/cmpxchg-local.h | 12 ++++++------
include/asm-generic/cmpxchg.h | 6 +++---
include/asm-generic/io.h | 16 ++++++++--------
4 files changed, 19 insertions(+), 19 deletions(-)
next reply other threads:[~2023-04-06 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 8:12 Arnd Bergmann [this message]
2023-04-06 17:04 ` Linus Torvalds
2023-04-06 20:02 ` Arnd Bergmann
2023-04-07 19:59 ` Linus Torvalds
2023-04-06 18:46 ` 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=f44680f5-df08-4034-9ed7-6d43ee4c4c2a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mev@rivosinc.com \
--cc=torvalds@linux-foundation.org \
--cc=vladimir.oltean@nxp.com \
/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
all inboxes | Powered by JetHome®