From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/iproute2: fix musl compile errors
Date: Thu, 15 Aug 2024 10:07:15 +0200 [thread overview]
Message-ID: <20240815100715.63a9e925@windsurf> (raw)
In-Reply-To: <Zr2s0yK7LbaHn+Uq@waldemar-brodkorb.de>
Hello Waldemar,
On Thu, 15 Aug 2024 09:22:59 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> It seems the Gentoo People already reported it upstream:
> https://marc.info/?l=linux-netdev&w=2&r=1&s=musl&q=b
>
> Would you like to update to this link or wait until the commits are
> upstream in git?
The link above is not very relevant, as it's a list of many e-mails.
The relevant link is:
https://marc.info/?l=linux-netdev&m=172278781323421&w=2
It is totally fine to use this link indeed for the Upstream: tag.
Basically, for the Upstream: tag we use what's available at the time we
add the patch in Buildroot: a link to the upstream commit if it's
already upstream, or a link to the mailing list, PR or issue ticket if
it's still pending 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
prev parent reply other threads:[~2024-08-15 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 18:57 [Buildroot] [PATCH] package/iproute2: fix musl compile errors Waldemar Brodkorb
2024-08-14 20:19 ` Thomas Petazzoni via buildroot
2024-08-15 7:22 ` Waldemar Brodkorb
2024-08-15 8:07 ` Thomas Petazzoni via buildroot [this message]
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=20240815100715.63a9e925@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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.