From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-amarula@amarulasolutions.com,
Dario Binacchi <dariobin@libero.it>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libmnl: remove dependency on kernel headers version
Date: Fri, 28 Jul 2023 22:57:06 +0200 [thread overview]
Message-ID: <20230728225706.11257a28@windsurf> (raw)
In-Reply-To: <20230602085741.3338373-1-dario.binacchi@amarulasolutions.com>
On Fri, 2 Jun 2023 10:57:41 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:
> As agreed in [1], now that the patch for including kernel headers has
> been applied upstream, we can remove the restrictions in Buildroot to
> avoid compilation failures.
>
> The patch is an adaptation of the one applied upstream.
>
> [1] https://patchwork.ozlabs.org/project/buildroot/patch/20230520210153.3944842-1-dario.binacchi@amarulasolutions.com/
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> ...ache-copy-of-can.h-and-can-netlink.h.patch | 548 ++++++++++++++++++
> package/libmnl/Config.in | 4 -
> package/libmnl/libmnl.mk | 1 +
> 3 files changed, 549 insertions(+), 4 deletions(-)
> create mode 100644 package/libmnl/0002-include-cache-copy-of-can.h-and-can-netlink.h.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-28 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 8:57 [Buildroot] [PATCH 1/1] package/libmnl: remove dependency on kernel headers version Dario Binacchi
2023-07-28 20:57 ` 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=20230728225706.11257a28@windsurf \
--to=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dariobin@libero.it \
--cc=linux-amarula@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox