From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
patches@lists.linux.dev, Mikulas Patocka <mpatocka@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: [PATCH 6.1 021/193] x86/asm: Fix an assembler warning with current binutils
Date: Sun, 22 Jan 2023 16:02:30 +0100 [thread overview]
Message-ID: <20230122150247.319977587@linuxfoundation.org> (raw)
In-Reply-To: <20230122150246.321043584@linuxfoundation.org>
From: Mikulas Patocka <mpatocka@redhat.com>
[ Upstream commit 55d235361fccef573990dfa5724ab453866e7816 ]
Fix a warning: "found `movsd'; assuming `movsl' was meant"
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
arch/x86/lib/iomap_copy_64.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/lib/iomap_copy_64.S b/arch/x86/lib/iomap_copy_64.S
index a1f9416bf67a..6ff2f56cb0f7 100644
--- a/arch/x86/lib/iomap_copy_64.S
+++ b/arch/x86/lib/iomap_copy_64.S
@@ -10,6 +10,6 @@
*/
SYM_FUNC_START(__iowrite32_copy)
movl %edx,%ecx
- rep movsd
+ rep movsl
RET
SYM_FUNC_END(__iowrite32_copy)
--
2.35.1
next prev parent reply other threads:[~2023-01-22 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 15:02 [PATCH 6.1 000/193] 6.1.8-rc1 review Greg Kroah-Hartman
2023-01-22 15:02 ` Greg Kroah-Hartman [this message]
2023-01-22 22:54 ` ogasawara takeshi
2023-01-23 4:09 ` Joel Fernandes
2023-01-23 7:42 ` Rudi Heitbaum
2023-01-23 8:03 ` Conor Dooley
2023-01-23 8:09 ` Naresh Kamboju
2023-01-23 19:11 ` Tom Saeger
2023-01-23 19:42 ` Tom Saeger
2023-01-24 12:11 ` Naresh Kamboju
2023-01-24 12:54 ` Tom Saeger
2023-01-24 15:57 ` Naresh Kamboju
2023-01-24 11:48 ` Naresh Kamboju
2023-01-23 9:03 ` Bagas Sanjaya
2023-01-23 9:07 ` Ron Economos
2023-01-23 11:15 ` Sudip Mukherjee
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=20230122150247.319977587@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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