All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Bonnefille via buildroot <buildroot@buildroot.org>
Cc: Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/starfive_spltool: new package
Date: Wed, 1 May 2024 20:53:47 +0200	[thread overview]
Message-ID: <20240501205347.41b44d6d@windsurf> (raw)
In-Reply-To: <20240403091952.653698-2-thomas.bonnefille@bootlin.com>

On Wed,  3 Apr 2024 11:14:39 +0200
Thomas Bonnefille via buildroot <buildroot@buildroot.org> wrote:

> This patch adds a new package for the Starfive SPL tool. It is used to
> add header to the Secondary Program Loader for board based on the
> Starfive JH7110 SoC.
> 
> Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
> ---
>  DEVELOPERS                                    |  3 +++
>  package/Config.in.host                        |  1 +
>  package/starfive-spltool/Config.in.host       |  8 ++++++++
>  .../starfive-spltool.hash                     |  2 ++
>  package/starfive-spltool/starfive-spltool.mk  | 20 +++++++++++++++++++
>  5 files changed, 34 insertions(+)
>  create mode 100644 package/starfive-spltool/Config.in.host
>  create mode 100644 package/starfive-spltool/JH7110_VF2_515_v5.11.3/starfive-spltool.hash
>  create mode 100644 package/starfive-spltool/starfive-spltool.mk

Thanks, I've applied to master after:

- fixing the commit title starfive_spltool -> starfive-spltool

- moving the .hash file directly under package/starfive-spltool/, using
  a versioned directory is only useful for packages for which multiple
  versions are supported, which is not the case here

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-05-01 18:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  9:14 [Buildroot] [PATCH 0/2] Add board support for Star64 Thomas Bonnefille via buildroot
2024-04-03  9:14 ` [Buildroot] [PATCH 1/2] package/starfive_spltool: new package Thomas Bonnefille via buildroot
2024-05-01 18:53   ` Thomas Petazzoni via buildroot [this message]
2024-04-03  9:14 ` [Buildroot] [PATCH 2/2] configs/pine64-star64: new defconfig Thomas Bonnefille via buildroot
2024-05-01 18:54   ` Thomas Petazzoni 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=20240501205347.41b44d6d@windsurf \
    --to=buildroot@buildroot.org \
    --cc=jagan@amarulasolutions.com \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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 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.