From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/linux-backports: bump version to 5.8
Date: Thu, 12 Nov 2020 22:01:03 +0100 [thread overview]
Message-ID: <20201112210103.GB60815@pevik> (raw)
In-Reply-To: <20201112120155.333290-2-ju.o@free.fr>
Hi Julien,
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
> Attempting to compile this package with newer Kernel version (e.g. v5.4)
> fails with message:
> Generating local configuration database from kernel ...Kernel version parse failed!
> Upgrading the package to 5.8 fixes this issue. Anyways, v4.4 is now
> rather old and beat the very purpose of having newer drivers in older
> kernels.
> Note that since backports tag v4.14-rc4-1, the requirement on minimal
> kernel version changed from 3.0 to 3.10. See commit [1].
Good catch!
In that case, can please person who merges this update
package/linux-backports/Config.in?
Kind regards,
Petr
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/commit/?id=a0d05f9f9ca50ea8b1d60726fac6b54167257e76
Update also package/linux-backports/Config.in:
diff --git package/linux-backports/Config.in package/linux-backports/Config.in
index 362e6e4bc7..251d202fd2 100644
--- package/linux-backports/Config.in
+++ package/linux-backports/Config.in
@@ -9,7 +9,7 @@ config BR2_PACKAGE_LINUX_BACKPORTS
recent kernels, backported to older ones.
This version of linux-backports supports kernels starting
- from 3.0.
+ from 3.10.
https://backports.wiki.kernel.org
next prev parent reply other threads:[~2020-11-12 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 16:22 [Buildroot] [PATCH 1/2] package/linux-backports: use buildroot host flex and bison Julien Olivain
2020-11-11 16:22 ` [Buildroot] [PATCH 2/2] package/linux-backports: bump version to 5.8 Julien Olivain
2020-11-11 21:47 ` Petr Vorel
2020-11-12 11:07 ` Julien Olivain
2020-11-11 21:06 ` [Buildroot] [PATCH 1/2] package/linux-backports: use buildroot host flex and bison Yann E. MORIN
2020-11-12 10:55 ` Julien Olivain
2020-11-11 21:35 ` Petr Vorel
2020-11-12 12:01 ` [Buildroot] [PATCH v2 1/2] package/linux-backports: use flex and bison to generate kconfig parser Julien Olivain
2020-11-12 12:01 ` [Buildroot] [PATCH v2 2/2] package/linux-backports: bump version to 5.8 Julien Olivain
2020-11-12 12:34 ` Baruch Siach
2020-11-12 19:30 ` Peter Seiderer
2020-11-12 21:01 ` Petr Vorel [this message]
2020-11-12 21:17 ` Yann E. MORIN
2020-11-12 21:24 ` Petr Vorel
[not found] ` <MW3PR11MB476417BF2CC5E2E72CA4AE36E9E60@MW3PR11MB4764.namprd11.prod.outlook.com>
2020-11-13 11:56 ` Julien Olivain
2020-11-12 20:53 ` [Buildroot] [PATCH v2 1/2] package/linux-backports: use flex and bison to generate kconfig parser Petr Vorel
2020-11-12 21:24 ` Yann E. MORIN
2020-11-13 13:09 ` [Buildroot] [PATCH v3 1/2] package/linux-backports: fix kernel version check Julien Olivain
2020-11-13 13:09 ` [Buildroot] [PATCH v3 2/2] package/linux-backports: bump version to 5.8 Julien Olivain
2020-11-13 19:07 ` Petr Vorel
2020-11-13 22:21 ` Yann E. MORIN
2020-11-17 21:26 ` Yann E. MORIN
2020-11-13 19:06 ` [Buildroot] [PATCH v3 1/2] package/linux-backports: fix kernel version check Petr Vorel
2020-11-13 22:08 ` Yann E. MORIN
2020-11-16 14:49 ` Peter Korsgaard
2020-11-15 15:09 ` [Buildroot] [PATCH v2 1/2] package/linux-backports: use flex and bison to generate kconfig parser 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=20201112210103.GB60815@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox