From: Petr Vorel <petr.vorel@gmail.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/iproute2: fix musl build
Date: Tue, 1 Feb 2022 00:05:19 +0100 [thread overview]
Message-ID: <YfhrL9CyQI2LDmKs@pevik> (raw)
In-Reply-To: <20220131230015.181368-1-fontaine.fabrice@gmail.com>
Hi Fabrice,
good catch!
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
...
> diff --git a/package/iproute2/0001-lib-fix-ax25-h-include-for-musl.patch b/package/iproute2/0001-lib-fix-ax25-h-include-for-musl.patch
...
> +[Retrieved from:
> +https://github.com/shemminger/iproute2/commit/8bced38a941a181f1468fa39541e872e51b6022f]
I'd use URL from primary git:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=8bced38a941a181f1468fa39541e872e51b6022f
Kind regards,
Petr
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-31 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 23:00 [Buildroot] [PATCH 1/1] package/iproute2: fix musl build Fabrice Fontaine
2022-01-31 23:05 ` Petr Vorel [this message]
2022-02-01 22:04 ` Arnout Vandecappelle
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=YfhrL9CyQI2LDmKs@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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