All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v2 5/6] tpm: Don't select LOG
Date: Wed, 20 Jan 2021 20:10:56 -0700	[thread overview]
Message-ID: <20210121031057.559301-6-sjg@chromium.org> (raw)
In-Reply-To: <20210121031057.559301-1-sjg@chromium.org>

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>
---

(no changes since v1)

 cmd/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/cmd/Kconfig b/cmd/Kconfig
index 0625ee4050f..7097cc1a145 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -2025,7 +2025,6 @@ config CMD_TPM_V1
 
 config CMD_TPM_V2
 	bool
-	select CMD_LOG
 
 config CMD_TPM
 	bool "Enable the 'tpm' command"
-- 
2.30.0.296.g2bfb1c46d8-goog

  parent reply	other threads:[~2021-01-21  3:10 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 ` Simon Glass [this message]
2021-03-15 15:52   ` [PATCH v2 5/6] tpm: Don't select LOG Tom Rini
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=20210121031057.559301-6-sjg@chromium.org \
    --to=sjg@chromium.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 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.