From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Bernd Kuhls <bernd@kuhls.net>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 2/5] package/busybox: disable tc to fix build with kernel >= 6.8
Date: Sun, 24 Mar 2024 18:45:58 +0100 [thread overview]
Message-ID: <87v85bh6ax.fsf@48ers.dk> (raw)
In-Reply-To: <0c44fe3f-e87e-42fe-bbab-743fee1306a3@mind.be> (Arnout Vandecappelle's message of "Sun, 24 Mar 2024 17:00:31 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 16/03/2024 20:25, Arnout Vandecappelle wrote:
>>
>>
>> On 16/03/2024 09:43, Bernd Kuhls wrote:
>>> For details see https://bugs.busybox.net/show_bug.cgi?id=15934
>>
>> I'm a bit afraid to apply this. Hopefully the issue will be fixed
>> at some point in busybox; then, we should probably revert this patch
>> (though honestly I don't know what tc is doing in the minimal
>> config...).
> I didn't apply this one nor the following two. I'm hoping the other
> maintainers can pipe up with ideas of how to best deal with this?
I also don't think having tc enabled by default makes a lot of
sense. Notice that Uwe recently posted a patch upstream to fix the build
issue:
http://lists.busybox.net/pipermail/busybox/2024-March/090678.html
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-24 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 8:43 [Buildroot] [PATCH 1/5] {toolchain, linux-headers}: add support for 6.7 headers Bernd Kuhls
2024-03-16 8:43 ` [Buildroot] [PATCH 2/5] package/busybox: disable tc to fix build with kernel >= 6.8 Bernd Kuhls
2024-03-16 19:25 ` Arnout Vandecappelle via buildroot
2024-03-24 16:00 ` Arnout Vandecappelle via buildroot
2024-03-24 17:45 ` Peter Korsgaard [this message]
2024-03-24 18:15 ` Arnout Vandecappelle via buildroot
2024-03-24 18:19 ` Arnout Vandecappelle via buildroot
2024-03-16 8:43 ` [Buildroot] [PATCH 3/5] {toolchain, linux-headers}: add support for 6.8 headers Bernd Kuhls
2024-03-16 8:43 ` [Buildroot] [PATCH 4/5] linux: bump latest version to 6.8 Bernd Kuhls
2024-03-25 10:07 ` Peter Korsgaard
2024-03-16 8:43 ` [Buildroot] [PATCH 5/5] {linux, linux-headers}: bump 4.19.x / 5.{4, 10, 15}.x / 6.{1, 6}.x series Bernd Kuhls
2024-03-24 16:00 ` Arnout Vandecappelle via buildroot
2024-03-25 10:05 ` Peter Korsgaard
2024-03-25 10:13 ` Peter Korsgaard
2024-03-24 15:59 ` [Buildroot] [PATCH 1/5] {toolchain, linux-headers}: add support for 6.7 headers Arnout Vandecappelle 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=87v85bh6ax.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=arnout@mind.be \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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