All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch for linux-headers
Date: Wed, 06 Jan 2021 00:07:23 +0100	[thread overview]
Message-ID: <87czyj3rv8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210105224940.GA158146@pevik> (Petr Vorel's message of "Tue, 5 Jan 2021 23:49:40 +0100")

>>>>> "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 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.

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

Ahh, ok.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2021-01-05 23:07 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 [this message]
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=87czyj3rv8.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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.