From: Alexey Dobriyan <adobriyan@gmail.com>
To: knscarlet@gnuweeb.org
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH 0/1] x86: change mov 0, %reg to xor %reg, %reg
Date: Mon, 8 Aug 2022 20:24:31 +0300 [thread overview]
Message-ID: <YvFGz3iIr5IJL+2V@localhost.localdomain> (raw)
Reviewed-by: Alexey Dobriyan <adobriyan@gmail.com>
Patch seems to be OK.
Minus interwebs points for using AT&T syntax.
Changing objtool to detect overlong "mov r32, imm32" automatically
would be cool.
next reply other threads:[~2022-08-08 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:24 Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-04 15:26 [PATCH 0/1] x86 change mov 0, %reg to xor %reg, %reg Kanna Scarlet
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=YvFGz3iIr5IJL+2V@localhost.localdomain \
--to=adobriyan@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=knscarlet@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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