From: Simon Glass <sjg@chromium.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] cmd: missing break in test_write_limit()
Date: Mon, 3 Apr 2023 06:45:05 +1200 [thread overview]
Message-ID: <CAPnjgZ0iBGadLP5YQE04R7un0P+gXkLwbcbGWcd+4mD=n6aQkQ@mail.gmail.com> (raw)
In-Reply-To: <20230402045154.8493-1-heinrich.schuchardt@canonical.com>
On Sun, 2 Apr 2023 at 16:51, Heinrich Schuchardt
<heinrich.schuchardt@canonical.com> wrote:
>
> In test_write_limit() an unintended fall-through occurs.
>
> Suggested-by: Simon Glass <sjg@chromium.org>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> cmd/tpm_test.c | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2023-04-02 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 4:51 [PATCH 1/1] cmd: missing break in test_write_limit() Heinrich Schuchardt
2023-04-02 18:45 ` Simon Glass [this message]
2023-04-03 5:52 ` Ilias Apalodimas
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='CAPnjgZ0iBGadLP5YQE04R7un0P+gXkLwbcbGWcd+4mD=n6aQkQ@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=u-boot@lists.denx.de \
/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;
as well as URLs for NNTP newsgroup(s).