From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] ebtables and musl
Date: Mon, 15 Jun 2020 06:55:27 +0300 [thread overview]
Message-ID: <87r1uhc79s.fsf@tarshish> (raw)
In-Reply-To: <8843cd27-6553-986e-92d5-e210a3f678f0@gmail.com>
Hi Florian,
On Mon, Jun 15 2020, Florian Fainelli wrote:
> On 6/13/2020 8:34 PM, Markus Mayer wrote:
>> On Sat, 13 Jun 2020 at 20:00, Baruch Siach <baruch@tkos.co.il> wrote:
>>> On Sat, Jun 13 2020, Markus Mayer wrote:
>>>
>>>> On Sat, 13 Jun 2020 at 05:43, Peter Seiderer <ps.report@gmx.net> wrote:
>>>>> On Fri, 12 Jun 2020 13:10:28 -0700, Markus Mayer <mmayer@broadcom.com> wrote:
>>>>>>> While we are on the topic of ebtables, why is buildroot still using
>>>>>>> v2.0.10-4 from 2014 when there is 2.0.11 from 2019 (as per
>>>>>>> http://ftp.netfilter.org/pub/ebtables/)? Is it just a matter of
>>>>>>> submitting a patch to update it or is there an underlying reason to
>>>>>>> keep the old version around?
>>>>>>
>>>>>> Probably not, care to send an ebtables update patch?
>>>>
>>>> Sure. I'll send a patch.
>>>
>>> We have a version upgrade patch in patchwork:
>>>
>>> http://patchwork.ozlabs.org/project/buildroot/patch/20200427212653.29933-1-ryanbarnett3 at gmail.com/
>>>
>>> You might want to test and contribute your Tested-by.
>>
>> Will do. I'll let you know how it goes.
>
> Would not these two patches be relevant for the kernel headers too:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da360299b6734135a5f66d7db458dcc7801c826a
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6926e041a8920c8ec27e4e155efa760aa01551fd
>
> which would not require patching ebtables or musl at all?
Buildroot allows the user to set the kernel version, or even provide a
whole kernel tree. This includes kernels older than v4.15/v4.16. Because
of that we can't rely on any given patch to apply to the kernel version
we happen to use for the toolchain.
The ebtables patch is no longer needed for version 2.0.11. The musl
patch however is still needed for compatibility with older kernels.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-06-15 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 20:10 [Buildroot] ebtables and musl Markus Mayer
2020-06-13 11:23 ` Peter Seiderer
2020-06-13 12:43 ` Peter Seiderer
2020-06-13 17:35 ` Markus Mayer
2020-06-14 3:00 ` Baruch Siach
2020-06-14 3:34 ` Markus Mayer
2020-06-14 21:34 ` Florian Fainelli
2020-06-15 3:03 ` Markus Mayer
2020-06-15 3:55 ` Baruch Siach [this message]
2020-06-15 23:02 ` Markus Mayer
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=87r1uhc79s.fsf@tarshish \
--to=baruch@tkos.co.il \
--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