From: Andreas Schwab <schwab@linux-m68k.org>
To: opensbi@lists.infradead.org
Subject: [PATCH 1/1] lib: utils: Simplify SET_ISA_EXT_MAP()
Date: Wed, 27 Sep 2023 18:47:29 +0200 [thread overview]
Message-ID: <87edijmula.fsf@igel.home> (raw)
In-Reply-To: <bdae373d-843d-4f5b-b7a8-24724f6eef2c@canonical.com> (Heinrich Schuchardt's message of "Wed, 27 Sep 2023 17:38:25 +0200")
On Sep 27 2023, Heinrich Schuchardt wrote:
> Just to be clear this is not what the incoming code did.
Though perhaps indented, given the use of continue throughout the loop.
The wrapping with do/while was probably an afterthought.
--
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2023-09-27 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 14:21 [PATCH 1/1] lib: utils: Simplify SET_ISA_EXT_MAP() Heinrich Schuchardt
2023-09-27 15:23 ` Xiang W
2023-09-27 15:38 ` Heinrich Schuchardt
2023-09-27 16:47 ` Andreas Schwab [this message]
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=87edijmula.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=opensbi@lists.infradead.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