All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Sune Brian <briansune@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v1] Cyclone V Board handsoff script
Date: Fri, 31 Oct 2025 11:46:13 -0600	[thread overview]
Message-ID: <20251031174613.GD6688@bill-the-cat> (raw)
In-Reply-To: <CAN7C2SCXWoi6XRKppKFUzPiUykYeQ0Mbm=S3dhALajP98S8rAA@mail.gmail.com>

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

On Sat, Nov 01, 2025 at 01:30:34AM +0800, Sune Brian wrote:
> > That's interesting. But that also does mean that someone needs to work
> > better with upstream about integration here as no, that's not where that
> > kind of tooling should live. At bare minimum it should be in
> > tools/something/ and have it's own requirements.txt file too for
> > whatever python modules it requires.
> 
> Do you mean I should move it to tool folder?

Yes, as a starting point this should live under tools/something/ and if
there's some way to add Makefile rules to automate xml -> c that would
probably help other users. But that's just a nice to have thing. Thanks!

-- 
Tom

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

  reply	other threads:[~2025-10-31 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30  0:33 [PATCH v1] Cyclone V Board handsoff script Brian Sune
2025-10-30 18:09 ` Tom Rini
2025-10-30 21:21   ` Sune Brian
2025-10-30 21:31     ` Sune Brian
2025-10-31 15:54       ` Tom Rini
2025-10-31 17:30         ` Sune Brian
2025-10-31 17:46           ` Tom Rini [this message]
2025-10-31 18:03             ` Sune Brian
2025-10-31 17:35         ` Sune Brian

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=20251031174613.GD6688@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=briansune@gmail.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.