From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: Julien Olivain <ju.o@free.fr>,
buildroot@buildroot.org, Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH v3 1/2] package/rasdaemon: Add rasdaemon package
Date: Wed, 17 Dec 2025 17:28:38 +0100 [thread overview]
Message-ID: <20251217172838.6ecf51e5@windsurf> (raw)
In-Reply-To: <d1fd147a-3d1a-4286-941d-05dc0e44ef3c@bootlin.com>
On Wed, 17 Dec 2025 16:30:22 +0100
Bastien Curutchet <bastien.curutchet@bootlin.com> wrote:
> Sure, I'll just wait for my PR to be merged before doing so.
Your upstream patch is simple enough that you can take it into
Buildroot and put it in package/rasdaemon/. Make sure to add an
Upstream: tag that points to the upstream PR. Indeed, it may be some
time before upstream (1) merges it and (2) makes a new release with it.
Thanks a lot!
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-17 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 14:08 [Buildroot] [PATCH v3 0/2] package: add rasdaemon support Bastien Curutchet via buildroot
2025-12-01 14:08 ` [Buildroot] [PATCH v3 1/2] package/rasdaemon: Add rasdaemon package Bastien Curutchet via buildroot
2025-12-01 16:26 ` Fiona Klute via buildroot
2025-12-13 22:11 ` Julien Olivain via buildroot
2025-12-17 15:30 ` Bastien Curutchet via buildroot
2025-12-17 16:28 ` Thomas Petazzoni via buildroot [this message]
2025-12-01 14:08 ` [Buildroot] [PATCH v3 2/2] support/testing: add rasdaemon tests Bastien Curutchet 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=20251217172838.6ecf51e5@windsurf \
--to=buildroot@buildroot.org \
--cc=bastien.curutchet@bootlin.com \
--cc=fiona.klute@gmx.de \
--cc=ju.o@free.fr \
--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.