U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Maxin John <maxin.john@gmail.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Simon Glass <sjg@chromium.org>, Mario Six <mario.six@gdsys.cc>,
	Daniel Golle <daniel@makrotopia.org>,
	u-boot@lists.u-boot-project.org
Subject: Re: [PATCH 1/2] configs: sandbox: Enable binop command
Date: Fri, 30 Oct 2026 10:39:53 -0600	[thread overview]
Message-ID: <20261030163953.GD3309461@bill-the-cat> (raw)
In-Reply-To: <CAMhs6Yxa0wdzkE3py=Ns5j+D8-8_+Z-ngnuxRKcTvQ+0qDpt-Q@mail.gmail.com>

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

On Fri, Oct 30, 2026 at 05:58:58PM +0200, Maxin John wrote:
> Hi Heinrich,
> 
> On Fri, Oct 30, 2026 at 1:26 AM Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > On 10/29/26 18:34, Maxin B. John wrote:
> > > Turn on CMD_BINOP for sandbox and sandbox64 so the binop tests are
> > > built and run in CI on both 32-bit and 64-bit builds.
> > >
> > > Signed-off-by: Maxin B. John <maxin.john@gmail.com>
> >
> > Which tests? I could not find any depending on CONFIG_CMD_BINOP.
> 
> This change is a follow-up to my recently submitted binop clean-up patch:
> https://lists.u-boot-project.org/pipermail/u-boot/2026-October/637804.html
> 
> Following the review comments on that patch, I have also submitted tests to
> improve binop test coverage:
> https://lists.u-boot-project.org/pipermail/u-boot/2026-October/637974.html
> 
> These tests depend on CONFIG_CMD_BINOP, which is why I enabled it in
> sandbox and sandbox64.
> 
> > HTML documentation for the command does not exist.
> > The online documentation leaves the user clueless:
> 
> Agreed. The documentation for binop is insufficient and could be improved.
> 
> > Usage:
> > binop op count [*]src1 [*]src2 [[*]dest]
> >      - compute binary operation of data at/in src1 and
> >        src2 (either *memaddr, env var name or hex string)
> >        and store result in/at dest, where op is one of
> >        xor, or, and.
> >
> > What is count good for?
> > What should a variable contain?
> >
> > Can we simply eliminate the command? It is only used by a single board.
> 
> I am not aware of any other users of this command apart from the
> gazerbeam board.
> Personally, I can work around its removal if that is what the
> maintainers decide.

Perhaps what's missing here is what your motivation is for this cleanup?

-- 
Tom

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

  reply	other threads:[~2026-10-30 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 17:34 [PATCH 0/2] test: cmd: add binop tests and enable on sandbox Maxin B. John
2026-10-29 17:34 ` [PATCH 1/2] configs: sandbox: Enable binop command Maxin B. John
2026-10-29 23:26   ` Heinrich Schuchardt
2026-10-30 15:58     ` Maxin John
2026-10-30 16:39       ` Tom Rini [this message]
2026-10-30 18:25         ` Maxin John
2026-10-30 18:34           ` Tom Rini
2026-10-29 17:34 ` [PATCH 2/2] test: cmd: add tests for the " Maxin B. John

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=20261030163953.GD3309461@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=daniel@makrotopia.org \
    --cc=mario.six@gdsys.cc \
    --cc=maxin.john@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=xypron.glpk@gmx.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