From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
igor.opaniuk@gmail.com, trini@konsulko.com
Cc: u-boot@lists.u-boot-project.org
Subject: Re: [PATCH] avb: fix missing break in avb_set_state() switch
Date: Wed, 02 Sep 2026 14:39:19 +0200 [thread overview]
Message-ID: <87fqzrn7yg.fsf@kernel.org> (raw)
In-Reply-To: <ya4gsjjicokwdqwvqwdoho6cf2iwo2ecrgvmfoappavszwml2l@tnxffaphc74s>
Hi Naveen,
Thank you for the patch.
On Tue, Sep 01, 2026 at 15:49, Naveen Kumar Chaudhary <naveen.osdev@gmail.com> wrote:
> The AVB_ORANGE case fell through into AVB_RED due to a missing break.
> It happened to be harmless since AVB_RED only breaks, but it trips
> -Wimplicit-fallthrough and is fragile against future changes. Add the
> missing break.
>
> Fixes: 5d4fd877733 ("avb2.0: add boot states and dm-verity support")
Fixes: 5d4fd877733 ("avb2.0: add boot states and dm-verity support")
Checkpatch.pl seems to warn here:
$ ./scripts/checkpatch.pl --git HEAD^..HEAD
WARNING: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 5d4fd8777337 ("avb2.0: add boot states and dm-verity support")'
#11:
So please replace this with:
Fixes: 5d4fd8777337 ("avb2.0: add boot states and dm-verity support")
(there is a missing '7' at the end of the sha1 in the original commit message)
Do you want to send a v2 with this fixed, or should I do the commit
message fixup when merging the patch into my tree?
> Signed-off-by: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>
> ---
> common/avb_verify.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/common/avb_verify.c b/common/avb_verify.c
> index b96cd1ebd7b..09f1534c3cc 100644
> --- a/common/avb_verify.c
> +++ b/common/avb_verify.c
> @@ -198,6 +198,7 @@ char *avb_set_state(AvbOps *ops, enum avb_boot_state boot_state)
> break;
> case AVB_ORANGE:
> cmdline = "androidboot.verifiedbootstate=orange";
> + break;
The change looks good to me, so:
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> case AVB_RED:
> break;
> }
> --
> 2.43.0
next prev parent reply other threads:[~2026-09-02 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 10:19 [PATCH] avb: fix missing break in avb_set_state() switch Naveen Kumar Chaudhary
2026-09-01 13:41 ` Simon Glass
2026-09-02 12:39 ` Mattijs Korpershoek [this message]
2026-09-09 9:05 ` Mattijs Korpershoek
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=87fqzrn7yg.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=igor.opaniuk@gmail.com \
--cc=naveen.osdev@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.