From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 5/6] tpm: Don't select LOG
Date: Mon, 15 Mar 2021 11:52:33 -0400 [thread overview]
Message-ID: <20210315155233.GI1310@bill-the-cat> (raw)
In-Reply-To: <20210121031057.559301-6-sjg@chromium.org>
On Wed, Jan 20, 2021 at 08:10:56PM -0700, Simon Glass wrote:
> We don't need to enable logging to run this command since the output will
> still appear. Drop the 'select'.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210315/5b94c6d0/attachment.sig>
next prev parent reply other threads:[~2021-03-15 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 3:10 [PATCH v2 0/6] log: Allow multiple lines and conversion to printf() Simon Glass
2021-01-21 3:10 ` [PATCH v2 1/6] log: Set up a flag byte for log records Simon Glass
2021-03-15 15:52 ` Tom Rini
2021-01-21 3:10 ` [PATCH v2 2/6] log: Handle line continuation Simon Glass
2021-03-15 15:52 ` Tom Rini
2021-01-21 3:10 ` [PATCH v2 3/6] log: Add return-checking macros for 0 being success Simon Glass
2021-03-15 15:52 ` Tom Rini
2021-01-21 3:10 ` [PATCH v2 4/6] sandbox: log: Avoid build error with !CONFIG_LOG Simon Glass
2021-01-21 3:10 ` [PATCH v2 5/6] tpm: Don't select LOG Simon Glass
2021-03-15 15:52 ` Tom Rini [this message]
2021-01-21 3:10 ` [PATCH v2 6/6] log: Convert log values to printf() if not enabled Simon Glass
2021-02-05 1:28 ` Sean Anderson
2021-02-05 3:31 ` Simon Glass
2021-03-14 19:33 ` Tom Rini
2021-03-14 20:32 ` Simon Glass
2021-02-05 1:20 ` [PATCH v2 0/6] log: Allow multiple lines and conversion to printf() Simon Glass
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=20210315155233.GI1310@bill-the-cat \
--to=trini@konsulko.com \
--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 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.