From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Javad Rahimi <javad321javad@gmail.com>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
"linux-amarula@amarulasolutions.com"
<linux-amarula@amarulasolutions.com>,
Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] boot/uboot: support System Control Processor (SCP) firmware blob
Date: Tue, 11 Feb 2025 09:52:55 +0000 [thread overview]
Message-ID: <Z6sd97YCGqHvWT7K@ryzen> (raw)
In-Reply-To: <Z6scc31LdTE21rU1@ryzen>
On Tue, Feb 11, 2025 at 10:46:27AM +0100, Niklas Cassel wrote:
> Hello Dario,
>
> here:
> https://lore.kernel.org/buildroot/a023971c7c8bfa4826a9a8721500c7ff@free.fr/
>
> Julien said that it does not need to be /dev/null,
> and that it works fine with just an empty string
> (if the default is the empty string).
Here is an example of a config option where the default is the empty string:
https://github.com/buildroot/buildroot/blob/2024.11/Config.in#L189
Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-11 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 9:33 [Buildroot] [PATCH 1/1] boot/uboot: support System Control Processor (SCP) firmware blob Dario Binacchi
2025-02-11 9:46 ` Niklas Cassel
2025-02-11 9:52 ` Niklas Cassel via buildroot [this message]
2025-02-11 9:53 ` Dario Binacchi
2025-02-11 10:13 ` Niklas Cassel via buildroot
2025-02-11 22:25 ` Julien Olivain
2025-02-11 16:48 ` Peter Korsgaard
2025-02-13 20:33 ` Arnout Vandecappelle via buildroot
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=Z6sd97YCGqHvWT7K@ryzen \
--to=buildroot@buildroot.org \
--cc=Niklas.Cassel@wdc.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=geomatsi@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=jagan@amarulasolutions.com \
--cc=javad321javad@gmail.com \
--cc=ju.o@free.fr \
--cc=linux-amarula@amarulasolutions.com \
--cc=m.niestroj@grinn-global.com \
/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