U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: u-boot@lists.denx.de, Casey Connolly <casey.connolly@linaro.org>
Subject: Re: [PATCH 8/8] cmd: config: allow simple filtering of output
Date: Wed, 1 Jul 2026 12:15:33 -0600	[thread overview]
Message-ID: <20260701181533.GT749385@bill-the-cat> (raw)
In-Reply-To: <20260701171535.906272-9-rv@rasmusvillemoes.dk>

[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]

On Wed, Jul 01, 2026 at 07:15:35PM +0200, Rasmus Villemoes wrote:

> When doing development, it can be quite useful to enable
> CONFIG_CMD_CONFIG, so that one can always check whether a config knob
> one has just enabled has actually made it to target.
> 
> Because sometimes, one doesn't flash the right binary, or maybe one
> has just done CONFIG_FOO=y in some config fragment, but that had no
> effect because one would also have to do CONFIG_BAR=y.
> 
> However, 2400+ lines of text are rather hard to read through. One
> probably uses a terminal emulator with capturing enabled, but
> searching back through the capture file is a little tedious, and one
> easily ends up finding something that doesn't pertain to the most
> recent 'config' command invocation.
> 
> So make it possible to limit the output to those lines containing a
> given string. Like the search functionality in menuconfig, make it
> case insensitive, because it is much more convenient to type "config
> pinctrl" than "config PINCTRL".
> 
> Since enabling CONFIG_CMD_CONFIG by itself adds over 10K of data, and
> that increases with every U-Boot release even if one doesn't add any
> new features to one's own defconfig (because the .config grows lots of
> "is not set"), I don't see any point in guarding this by some
> CONFIG_CMD_CONFIG_GREP.
> 
> Signed-off-by: Rasmus Villemoes <rv@rasmusvillemoes.dk>
> ---
>  cmd/config.c | 25 ++++++++++++++++++++++---
>  1 file changed, 22 insertions(+), 3 deletions(-)

Reasonable addition and explanation (and having switched to tmux from
screen, I don't have an easy capture anymore, the one regret I have) so
this is very useful. My only feedback is that you should add
doc/usage/cmd/config.rst now too.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-07-01 18:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 17:15 [PATCH 0/8] some string cleanup, and a tweak of the "config" command Rasmus Villemoes
2026-07-01 17:15 ` [PATCH 1/8] sh: clean up asm/string.h Rasmus Villemoes
2026-07-02  8:29   ` Simon Glass
2026-07-01 17:15 ` [PATCH 2/8] string: correct prototype of strchrnul() Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-01 17:15 ` [PATCH 3/8] string: correct documentation for strstr and strnstr Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-01 17:15 ` [PATCH 4/8] string: remove unused strswab() function Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-01 17:15 ` [PATCH 5/8] string: remove more pointless __HAVE_ARCH_STR* Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-01 17:15 ` [PATCH 6/8] string: add strcasestr() Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-08 18:40     ` Rasmus Villemoes
2026-07-08 19:09       ` Tom Rini
2026-07-01 17:15 ` [PATCH 7/8] test: string: add test of new strcasestr() function Rasmus Villemoes
2026-07-02  8:30   ` Simon Glass
2026-07-01 17:15 ` [PATCH 8/8] cmd: config: allow simple filtering of output Rasmus Villemoes
2026-07-01 18:15   ` Tom Rini [this message]
2026-07-02  8:30   ` Simon Glass
2026-07-08 18:59     ` Rasmus Villemoes

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=20260701181533.GT749385@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=casey.connolly@linaro.org \
    --cc=rv@rasmusvillemoes.dk \
    --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