From: Yu-Chien Peter Lin <peterlin@andestech.com>
To: opensbi@lists.infradead.org
Subject: [PATCH] lib: utils: fdt_fixup: Fix compile error
Date: Sun, 19 Feb 2023 17:44:19 +0000 [thread overview]
Message-ID: <Y/Jf2w3TaEfRiMlz@APC323> (raw)
In-Reply-To: <874jrij9zm.fsf@linux-m68k.org>
On Sun, Feb 19, 2023 at 10:11:09AM +0100, Andreas Schwab wrote:
> On Feb 19 2023, Yu Chien Peter Lin wrote:
>
> > Thus move the label "next_entry" to the beginning of the for loop.
>
> This changes the semantics, because jumping to the top of the loop skips
> the update expression.
>
> --
> 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."
Hi Andreas,
Thanks for pointing this out!
Hi Xiang,
I've set the patch state to superseded,
Could you send your fix?
Thanks
Peter Lin
next prev parent reply other threads:[~2023-02-19 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 6:33 [PATCH] lib: utils: fdt_fixup: Fix compile error Yu Chien Peter Lin
2023-02-19 9:11 ` Andreas Schwab
2023-02-19 17:44 ` Yu-Chien Peter Lin [this message]
2023-02-19 9:28 ` Xiang W
-- strict thread matches above, loose matches on Subject: below --
2023-02-19 10:15 Xiang W
2023-02-19 10:20 ` Andreas Schwab
2023-02-19 12:41 ` Xiang W
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=Y/Jf2w3TaEfRiMlz@APC323 \
--to=peterlin@andestech.com \
--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