From: Adam Duskett <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] kmod: bump to 25
Date: Mon, 20 Aug 2018 09:53:29 -0700 [thread overview]
Message-ID: <20180820165329.10083-2-aduskett@gmail.com> (raw)
In-Reply-To: <20180820165329.10083-1-aduskett@gmail.com>
From: Adam Duskett <aduskett@greenlots.com>
With the introduction of Python3.7.0, kmod needs to be bumped to
version 25.
Fixes:
5ba7f2e9d0802890e275f7da160ad0aad87b6f56
Signed-off-by: Adam Duskett <aduskett@greenlots.com>
---
....c-assert_cc-can-only-be-used-inside-func.patch | 56 ----------------------
package/kmod/kmod.hash | 2 +-
package/kmod/kmod.mk | 2 +-
3 files changed, 2 insertions(+), 58 deletions(-)
delete mode 100644 package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
diff --git a/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch b/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
deleted file mode 100644
index 09fe252..0000000
--- a/package/kmod/0002-shared-util.c-assert_cc-can-only-be-used-inside-func.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 7cd698eb31059012305d8bb7516577c8cd383e32 Mon Sep 17 00:00:00 2001
-From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-Date: Sat, 3 Jun 2017 16:52:37 +0200
-Subject: [PATCH] shared/util.c: assert_cc() can only be used inside functions
-
-shared/macro.h has two versions of assert_cc, one that uses gcc
-_Static_assert(), which requires recent enough gcc versions, and one
-that uses a fake array to trigger a build error. The latter can only
-work inside functions, so assert_cc() should only be used inside
-functions.
-
-Fixes the following build failure when building kmod with old gcc
-versions such as gcc 4.3.x:
-
-shared/util.c:52: error: expected identifier or '(' before 'do'
-shared/util.c:52: error: expected identifier or '(' before 'while'
-
-Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
----
- shared/util.c | 6 ++++--
- 1 file changed, 4 insertions(+), 2 deletions(-)
-
-diff --git a/shared/util.c b/shared/util.c
-index 9de080a..fd2028d 100644
---- a/shared/util.c
-+++ b/shared/util.c
-@@ -49,8 +49,6 @@ static const struct kmod_ext {
- { }
- };
-
--assert_cc(EAGAIN == EWOULDBLOCK);
--
- /* string handling functions and memory allocations */
- /* ************************************************************************ */
-
-@@ -201,6 +199,8 @@ ssize_t read_str_safe(int fd, char *buf, size_t buflen)
- size_t todo = buflen - 1;
- size_t done = 0;
-
-+ assert_cc(EAGAIN == EWOULDBLOCK);
-+
- do {
- ssize_t r = read(fd, buf + done, todo);
-
-@@ -226,6 +226,8 @@ ssize_t write_str_safe(int fd, const char *buf, size_t buflen)
- size_t todo = buflen;
- size_t done = 0;
-
-+ assert_cc(EAGAIN == EWOULDBLOCK);
-+
- do {
- ssize_t r = write(fd, buf + done, todo);
-
---
-2.7.4
-
diff --git a/package/kmod/kmod.hash b/package/kmod/kmod.hash
index be350c4..0e8f034 100644
--- a/package/kmod/kmod.hash
+++ b/package/kmod/kmod.hash
@@ -1,2 +1,2 @@
# From https://www.kernel.org/pub/linux/utils/kernel/kmod/sha256sums.asc
-sha256 610b8d1df172acc39a4fdf1eaa47a57b04873c82f32152e7a62e29b6ff9cb397 kmod-24.tar.xz
+sha256 7165e6496656159dcb909a91ed708a0fe273a4b128b4b1dc997ccb5189eef1cd kmod-25.tar.xz
diff --git a/package/kmod/kmod.mk b/package/kmod/kmod.mk
index 7c796ab..c165ea3 100644
--- a/package/kmod/kmod.mk
+++ b/package/kmod/kmod.mk
@@ -4,7 +4,7 @@
#
################################################################################
-KMOD_VERSION = 24
+KMOD_VERSION = 25
KMOD_SOURCE = kmod-$(KMOD_VERSION).tar.xz
KMOD_SITE = $(BR2_KERNEL_MIRROR)/linux/utils/kernel/kmod
KMOD_INSTALL_STAGING = YES
--
1.8.3.1
next prev parent reply other threads:[~2018-08-20 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 16:53 [Buildroot] [PATCH/next 2/2] python-setuptools: bump to 40.1.0 Adam Duskett
2018-08-20 16:53 ` Adam Duskett [this message]
2018-08-20 20:24 ` [Buildroot] [PATCH/next 2/2] kmod: bump to 25 Thomas Petazzoni
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=20180820165329.10083-2-aduskett@gmail.com \
--to=aduskett@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.