From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] rules/module-init-tools: Enable zlib compression support.
Date: Fri, 8 Oct 2021 22:28:37 +0200 [thread overview]
Message-ID: <9b938155-e5c6-60ff-581f-8327b868d6d5@t2data.com> (raw)
In-Reply-To: <20210929112610.GC2560099@pengutronix.de>
On 9/29/21 13:26, Michael Olbrich wrote:
> On Thu, Sep 09, 2021 at 02:01:16PM +0200, Christian Melki wrote:
>> Let old and trusty module-init-tools handle zlib compressed kernel modules.
>
> Any reason why you use this instead of libkmod? The module-init-tools are
> no longer maintained, so I would actually prefer to move the package to
> staging and remove it eventually. Unless there is a specific use-case for
> them that does not work with libkmod?
>
> Michael
>
Nope. No reason. Just compressed module support in case someone uses it.
I don't mind either way. But if it doesn't move to staging then you
might as well add compressed module support? I see no harm.
While we're at it.. Why "staging" for obsoleted packages?
How about obsolete for obsolescence and staging for the fashionable
kids? I think it makes it a whole lot clearer if you're unfamiliar with
whatever package.
>> ---
>> rules/module-init-tools.in | 7 +++++++
>> rules/module-init-tools.make | 4 +++-
>> 2 files changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/rules/module-init-tools.in b/rules/module-init-tools.in
>> index 765de6b97..010f68bf2 100644
>> --- a/rules/module-init-tools.in
>> +++ b/rules/module-init-tools.in
>> @@ -4,6 +4,7 @@
>> menuconfig MODULE_INIT_TOOLS
>> tristate
>> prompt "module-init-tools "
>> + select ZLIB if MODULE_INIT_TOOLS_ZLIB
>> help
>> This package contains a set of programs for loading, inserting
>> and removing kernel modules for Linux (versions 2.5.48 and
>> @@ -11,6 +12,12 @@ menuconfig MODULE_INIT_TOOLS
>>
>> if MODULE_INIT_TOOLS
>>
>> +config MODULE_INIT_TOOLS_ZLIB
>> + bool
>> + prompt "zlib compression support"
>> + help
>> + Enable support for gz compressed kernel modules
>> +
>> config MODULE_INIT_TOOLS_INSMOD
>> bool
>> prompt "Install insmod on target"
>> diff --git a/rules/module-init-tools.make b/rules/module-init-tools.make
>> index a4aa68175..da5a892bf 100644
>> --- a/rules/module-init-tools.make
>> +++ b/rules/module-init-tools.make
>> @@ -35,7 +35,9 @@ MODULE_INIT_TOOLS_MAKEVARS := MAN5="" MAN8=""
>> #
>> # autoconf
>> #
>> -MODULE_INIT_TOOLS_AUTOCONF := $(CROSS_AUTOCONF_USR)
>> +MODULE_INIT_TOOLS_AUTOCONF := \
>> + $(CROSS_AUTOCONF_USR) \
>> + --$(call ptx/endis, PTXCONF_MODULE_INIT_TOOLS_ZLIB)-zlib-dynamic
>>
>> # ----------------------------------------------------------------------------
>> # Target-Install
>> --
>> 2.30.2
>>
>>
>> _______________________________________________
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>>
>
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-10-08 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 12:01 Christian Melki
2021-09-29 11:26 ` Michael Olbrich
2021-10-08 20:28 ` Christian Melki [this message]
2021-10-11 6:48 ` Michael Olbrich
2021-10-11 7:44 ` Christian Melki
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=9b938155-e5c6-60ff-581f-8327b868d6d5@t2data.com \
--to=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