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
Subject: [PATCH 5.4 109/134] x86/asm: Fix an assembler warning with current binutils
Date: Fri, 3 Feb 2023 11:13:34 +0100 [thread overview]
Message-ID: <20230203101028.732656549@linuxfoundation.org> (raw)
In-Reply-To: <20230203101023.832083974@linuxfoundation.org>
From: Mikulas Patocka <mpatocka@redhat.com>
commit 55d235361fccef573990dfa5724ab453866e7816 upstream.
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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
arch/x86/lib/iomap_copy_64.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/lib/iomap_copy_64.S
+++ b/arch/x86/lib/iomap_copy_64.S
@@ -10,6 +10,6 @@
*/
ENTRY(__iowrite32_copy)
movl %edx,%ecx
- rep movsd
+ rep movsl
ret
ENDPROC(__iowrite32_copy)
next prev parent reply other threads:[~2023-02-03 10:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 10:11 [PATCH 5.4 000/134] 5.4.231-rc1 review Greg Kroah-Hartman
2023-02-03 10:13 ` Greg Kroah-Hartman [this message]
2023-02-03 15:56 ` Guenter Roeck
2023-02-03 16:45 ` Greg Kroah-Hartman
2023-02-03 17:18 ` Guenter Roeck
2023-02-03 18:54 ` Eric Biggers
2023-02-03 19:07 ` Eric Biggers
2023-02-03 19:28 ` Guenter Roeck
2023-02-03 19:49 ` Eric Biggers
2023-02-04 7:59 ` Greg Kroah-Hartman
2023-02-04 13:48 ` Sasha Levin
2023-02-04 13:59 ` Greg Kroah-Hartman
2023-02-04 16:08 ` Sasha Levin
2023-02-04 16:23 ` Greg Kroah-Hartman
2023-02-03 18:41 ` Florian Fainelli
2023-02-04 1:01 ` Shuah Khan
2023-02-04 1:50 ` Guenter Roeck
2023-02-04 9:00 ` Naresh Kamboju
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=20230203101028.732656549@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=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