mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libkmod: Version bump. 29 -> 30.
Date: Thu,  4 Aug 2022 17:14:03 +0200	[thread overview]
Message-ID: <20220804151403.174409-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220714164106.524329-1-christian.melki@t2data.com>

Thanks, applied as 3c090b5deee8239699a5dd3a33b5a6998b7666a7.

Michael

[sent from post-receive hook]

On Thu, 04 Aug 2022 17:14:03 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Various improvements and fixes.
> https://lwn.net/Articles/899526/
> 
> Including one speedup, where depmod would spend
> a lot of time, in the order of million syscalls,
> resolving modules on target.
> 
> Another useful addition is the retry removal backoff
> for modules that are still in use.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220714164106.524329-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/libkmod.make b/rules/libkmod.make
> index 8a085601a367..f9076f09f588 100644
> --- a/rules/libkmod.make
> +++ b/rules/libkmod.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBKMOD) += libkmod
>  #
>  # Paths and names
>  #
> -LIBKMOD_VERSION	:= 29
> -LIBKMOD_MD5	:= e81e63acd80697d001c8d85c1acb38a0
> +LIBKMOD_VERSION	:= 30
> +LIBKMOD_MD5	:= 85202f0740a75eb52f2163c776f9b564
>  LIBKMOD		:= kmod-$(LIBKMOD_VERSION)
>  LIBKMOD_SUFFIX	:= tar.xz
>  LIBKMOD_URL	:= $(call ptx/mirror, KERNEL, utils/kernel/kmod/$(LIBKMOD).$(LIBKMOD_SUFFIX))



      reply	other threads:[~2022-08-04 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 16:41 [ptxdist] [PATCH] " Christian Melki
2022-08-04 15:14 ` Michael Olbrich [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=20220804151403.174409-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /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