From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/iproute2: fixup Upstream url
Date: Thu, 15 Aug 2024 14:12:00 +0200 [thread overview]
Message-ID: <Zr3wkHvltQqq4L7Q@waldemar-brodkorb.de> (raw)
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
...ix-implicit-declaration-of-function-basename-in-gcc.patch | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/package/iproute2/0002-Fix-implicit-declaration-of-function-basename-in-gcc.patch b/package/iproute2/0002-Fix-implicit-declaration-of-function-basename-in-gcc.patch
index 7ebbb49816..ff1ddd144a 100644
--- a/package/iproute2/0002-Fix-implicit-declaration-of-function-basename-in-gcc.patch
+++ b/package/iproute2/0002-Fix-implicit-declaration-of-function-basename-in-gcc.patch
@@ -4,9 +4,12 @@ Date: Wed, 14 Aug 2024 19:43:44 +0200
Subject: [PATCH] Fix implicit declaration of function basename in gcc-14.x
From Alpine Linux.
+https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/iproute2/basename.patch?ref_type=heads
+
+But also reported Upstream via netdev mailinglist by Gentoo people.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
-Upstream: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/iproute2/basename.patch?ref_type=heads
+Upstream: https://marc.info/?l=linux-netdev&m=172278781323421&w=2
---
rdma/rdma.c | 3 +++
1 file changed, 3 insertions(+)
--
2.30.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-08-15 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 12:12 Waldemar Brodkorb [this message]
2024-08-15 12:49 ` [Buildroot] [PATCH] package/iproute2: fixup Upstream url 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=Zr3wkHvltQqq4L7Q@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox