From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch for linux-headers
Date: Thu, 17 Dec 2020 01:30:06 +0100 [thread overview]
Message-ID: <20201217003006.GA343694@pevik> (raw)
Hi,
I wonder if it's allowed to add patch to add patch for linux-headers.
There would have to be more versions for the patch (due headers being built for
more versions). I'd like to use my upstreamed patch [1] which fixes
"redefinition of struct sysinfo" build failure on MUSL.
This so far required to patch affected packages or simply disable them
(depends on !BR2_TOOLCHAIN_USES_MUSL).
Actually, much simpler patch from Khem Raj could be used [2].
Kind regards,
Petr
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a85cbe6159ffc973e5702f70a3bd5185f8f3c38d
[2] https://git.alpinelinux.org/aports/tree/main/linux-headers/0003-remove-inclusion-of-sysinfo.h-in-kernel.h.patch
next reply other threads:[~2020-12-17 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 0:30 Petr Vorel [this message]
2021-01-05 21:35 ` [Buildroot] Patch for linux-headers Peter Korsgaard
2021-01-05 22:49 ` Petr Vorel
2021-01-05 23:07 ` Peter Korsgaard
2021-01-07 1:23 ` Petr Vorel
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=20201217003006.GA343694@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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