From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ltrace: fix musl build
Date: Sat, 4 Nov 2023 18:41:42 +0100 [thread overview]
Message-ID: <20231104184142.24723c2d@windsurf> (raw)
In-Reply-To: <20231104155857.110364-1-fontaine.fabrice@gmail.com>
On Sat, 4 Nov 2023 16:58:57 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following musl build failure raised since commit
> bf9583a50276f52edbc37d9f85df5f2cc7fdb5dc:
>
> checking host system type... mips-buildroot-linux-musl
>
> Fixes:
> - http://autobuild.buildroot.org/results/a3a5c46e8562d3f091a9b4b205322168fbf9d16b
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Thanks for solving this issue.
> +Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +Upstream: unsent yet
Doesn't that defeat the purpose of the Upstream: flag entirely? Isn't
the idea precisely to strongly encourage (not to say "require") that
patches be sent upstream?
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:[~2023-11-04 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 15:58 [Buildroot] [PATCH 1/1] package/ltrace: fix musl build Fabrice Fontaine
2023-11-04 17:41 ` Thomas Petazzoni via buildroot [this message]
2024-10-26 17:05 ` 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=20231104184142.24723c2d@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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.