From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kmod: Update to 30
Date: Thu, 28 Jul 2022 20:37:57 +0100 [thread overview]
Message-ID: <F254443D-F297-46D5-BCE6-5DBD20D1B8B3@ipfire.org> (raw)
In-Reply-To: <aead8edb-b86a-da62-1407-4dc35b791d36@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 28 Jul 2022, at 11:26, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Please refer to the tarballs's NEWS file for release announcements.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/common/kmod | 2 +-
> lfs/kmod | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/kmod b/config/rootfiles/common/kmod
> index f46db860b..78971ea22 100644
> --- a/config/rootfiles/common/kmod
> +++ b/config/rootfiles/common/kmod
> @@ -9,6 +9,6 @@ sbin/rmmod
> #usr/lib/libkmod.la
> #usr/lib/libkmod.so
> usr/lib/libkmod.so.2
> -usr/lib/libkmod.so.2.3.7
> +usr/lib/libkmod.so.2.4.0
> #usr/lib/pkgconfig/libkmod.pc
> #usr/share/bash-completion/completions/kmod
> diff --git a/lfs/kmod b/lfs/kmod
> index ad12065c7..89e196252 100644
> --- a/lfs/kmod
> +++ b/lfs/kmod
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 29
> +VER = 30
>
> THISAPP = kmod-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 1362b6e7c07f66594074f07239d0f7a64e6efeb928483ed027b22a4ac77b916c631d1c03780b0515714a87847a716c35341edb1ced04a1795b4c7f8942d3207a
> +$(DL_FILE)_BLAKE2 = c5cb690dbb8fad66ac603648ff330794b417ff2fa2f8f61b6e9cb76dab93f984128b3d83a826203f39f3fb94f174f0db7395db6a47e52e8b7c561486f9d00778
>
> install : $(TARGET)
>
> --
> 2.35.3
prev parent reply other threads:[~2022-07-28 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 10:26 Peter Müller
2022-07-28 19:37 ` Michael Tremer [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=F254443D-F297-46D5-BCE6-5DBD20D1B8B3@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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