From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Un1q32 <joey.t.reinhart@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/busybox: patch to fix tc build on 6.8+ kernels
Date: Fri, 23 Aug 2024 17:48:40 +0200 [thread overview]
Message-ID: <20240823174840.40aacd0d@windsurf> (raw)
In-Reply-To: <20240823090939.79455-1-joey.t.reinhart@gmail.com>
Hello,
On Fri, 23 Aug 2024 05:09:39 -0400
Un1q32 <joey.t.reinhart@gmail.com> wrote:
> Signed-off-by: Un1q32 <joey.t.reinhart@gmail.com>
Thanks a lot for the patch!
We need patches to be sent with a real-name... especially when in fact
your real name is clearly visible in your e-mail address.
> diff --git a/package/busybox/0010-tc-build-fails-on-kernel-6.8.patch b/package/busybox/0010-tc-build-fails-on-kernel-6.8.patch
> new file mode 100644
> index 0000000000..95f2585c21
> --- /dev/null
> +++ b/package/busybox/0010-tc-build-fails-on-kernel-6.8.patch
> @@ -0,0 +1,55 @@
> +http://lists.busybox.net/pipermail/busybox/2024-March/090678.html
> +https://bugs.gentoo.org/926872
> +
> +Linux v6.8-rc1 removed the definitions related to CBQ making tc fail to
> +build. Add some #ifdefs to handle this missing support.
> +
> +Signed-off-by: Un1q32 <joey.t.reinhart@gmail.com>
Could you please send a patch generated by Git format-patch, and that
keep the original authorship? It should have an Upstream: tag pointing
to where it has been submitted upstream, and indeed your Signed-off-by
line.
See
package/busybox/0009-menuconfig-gcc-failing-saying-ncurses-is-not-found.patch
for an example where it has been done the way we expect.
Could you come up with a v2 of your patch that addresses those small
details?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-23 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 9:09 [Buildroot] [PATCH 1/1] package/busybox: patch to fix tc build on 6.8+ kernels Un1q32
2024-08-23 15:48 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 17:06 Bernd Kuhls
2024-09-23 19:13 ` Yann E. MORIN
2024-10-12 14:53 ` Peter Korsgaard
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=20240823174840.40aacd0d@windsurf \
--to=buildroot@buildroot.org \
--cc=joey.t.reinhart@gmail.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