All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	 U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2 3/3] sandbox: test: activate tests for the command LOG
Date: Thu, 27 Jan 2022 08:05:49 -0700	[thread overview]
Message-ID: <CAPnjgZ1r2es+rUV2QOJnBo70EOr5EYiJSkMCCY-ZcD-C74LBWw@mail.gmail.com> (raw)
In-Reply-To: <20220117164919.v2.3.I8b2905e3dfc95c21afd004977b40787144509b5c@changeid>

On Mon, 17 Jan 2022 at 08:49, Patrick Delaunay
<patrick.delaunay@foss.st.com> wrote:
>
> Activate the CONFIG_CMD_LOG in sandbox to execute the LOG tests
> by default and correct the test log format after 72fa1ad8d9 ("log: Allow
> padding of the function name").
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> ---
>
> Changes in v2:
> - update commit message "sandox" => "sandbox"
>
>  configs/sandbox_defconfig | 2 +-
>  test/py/tests/test_log.py | 8 ++++----
>  2 files changed, 5 insertions(+), 5 deletions(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>



activate tests for the command LOG

      reply	other threads:[~2022-01-27 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 15:49 [PATCH v2 0/3] sandbox: test: activate tests for the command LOG Patrick Delaunay
2022-01-17 15:49 ` [PATCH v2 1/3] dm: fix up documentation for uclass_get_by_name_len Patrick Delaunay
2022-01-27 15:05   ` Simon Glass
2022-01-17 15:49 ` [PATCH v2 2/3] dm: compare full name in uclass_get_by_name Patrick Delaunay
2022-01-27 15:05   ` Simon Glass
2022-01-17 15:49 ` [PATCH v2 3/3] sandbox: test: activate tests for the command LOG Patrick Delaunay
2022-01-27 15:05   ` Simon Glass [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=CAPnjgZ1r2es+rUV2QOJnBo70EOr5EYiJSkMCCY-ZcD-C74LBWw@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=patrick.delaunay@foss.st.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-stm32@st-md-mailman.stormreply.com \
    /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.