All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch for linux-headers
Date: Thu, 7 Jan 2021 02:23:42 +0100	[thread overview]
Message-ID: <20210107012342.GA98187@pevik> (raw)
In-Reply-To: <87czyj3rv8.fsf@dell.be.48ers.dk>

Hi Peter,

> >>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes:

> Hi,

>  >> It can be done if needed, but it is naturally easier to handle
>  >> without.
>  > Understand. More versions and kernel checking would be needed.
>  > I implemented it, but IMHO it'd have to also require Buildroot toolchain
>  > rebuild.

> Indeed.
I backported it to all LTS and stable branches (except 5.9 which is EOL)
It has been released to some of them, for the rest the patch is in
stable-queue.git => will be released soon.

>  >> I noticed that you got some patches applied to the stable
>  >> kernels related to this recently - Do those fix the issues, or is an
>  >> additional patch needed?
>  > Yes, it fixes the issue. Thus no patching is needed.

> Ok, great!

>  > OK, we need to wait till kernel stable releases, update kernel versions in
>  > Buildroot. But IMHO it still requires Buildroot toolchain rebuild. Or am I wrong?

> Yes, the external toolchains will need to be rebuilt, but perhaps we can
> blacklist those in the autobuilders until the toolchains are all rebuilt.
Do you mean to disable MUSL based toolchains for affected packages?
I'm carrying patch for LTP, which is not going to be upstreamed.
Sure, I could drop this patch and add: depends on !BR2_TOOLCHAIN_USES_MUSL,
but I expect more packages affected by <linux/sysinfo.h> bug.

>  > BTW I'm waiting for it for iproute2 upgrade (originally [1] and [2], now [3]).

> Ahh, ok.
I've prepared package for v5.8.0 which was blocked by this, then v5.9.0.
There is already v5.10.0. I'm not sure what is better: allow BR2_TOOLCHAIN_USES_UCLIBC
to have iproute2, but block new features (we still have v5.7.0).

Kind regards,
Petr

      reply	other threads:[~2021-01-07  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  0:30 [Buildroot] Patch for linux-headers Petr Vorel
2021-01-05 21:35 ` Peter Korsgaard
2021-01-05 22:49   ` Petr Vorel
2021-01-05 23:07     ` Peter Korsgaard
2021-01-07  1:23       ` Petr Vorel [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=20210107012342.GA98187@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.