From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Andreas Ziegler <br025@umbiko.net>
Subject: Re: [Buildroot] [PATCH/next 1/2] package/libsidplayfp: new package
Date: Fri, 5 Dec 2025 20:35:40 +0100 [thread overview]
Message-ID: <20251205203540.7fe5d366@windsurf> (raw)
In-Reply-To: <20251205193057.1884663-1-bernd@kuhls.net>
Hello Bernd,
On Fri, 5 Dec 2025 20:30:56 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> Replaces libsidplay2 as dependency in mpd 0.24.0:
> https://github.com/MusicPlayerDaemon/MPD/blob/v0.24.6/NEWS#L125
> https://github.com/MusicPlayerDaemon/MPD/commit/7e2538e07a80bd12baf2e7c328e7d1a64eb434f9
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/Config.in | 1 +
> package/libsidplayfp/Config.in | 13 +++++++++++++
> package/libsidplayfp/libsidplayfp.hash | 3 +++
> package/libsidplayfp/libsidplayfp.mk | 20 ++++++++++++++++++++
> 4 files changed, 37 insertions(+)
> create mode 100644 package/libsidplayfp/Config.in
> create mode 100644 package/libsidplayfp/libsidplayfp.hash
> create mode 100644 package/libsidplayfp/libsidplayfp.mk
Thanks for your patch!
Could you add an entry in the DEVELOPERS file for this new package?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-05 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 19:30 [Buildroot] [PATCH/next 1/2] package/libsidplayfp: new package Bernd Kuhls
2025-12-05 19:30 ` [Buildroot] [PATCH/next 2/2] package/mpd: switch from libsidplay2 to libsidplayfp Bernd Kuhls
2025-12-06 4:51 ` Andreas Ziegler
2025-12-05 19:35 ` Thomas Petazzoni via buildroot [this message]
2025-12-06 5:18 ` [Buildroot] [PATCH/next 1/2] package/libsidplayfp: new package Andreas Ziegler
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=20251205203540.7fe5d366@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=br025@umbiko.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox