From: Michal Marek <mmarek@suse.cz>
To: Rusty Russell <rusty@rustcorp.com.au>, Andreas Mohr <andi@lisas.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bertrand Jacquin <beber@meleeweb.net>, Marco d'Itri <md@linux.it>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH] modules: CONFIG_MODULE_COMPRESS: add hint that userspace support may easily be missing.
Date: Wed, 03 Jun 2015 14:04:24 +0200 [thread overview]
Message-ID: <556EED48.6010804@suse.cz> (raw)
In-Reply-To: <87r3pwgd0b.fsf@rustcorp.com.au>
On 2015-06-01 08:26, Rusty Russell wrote:
> Andreas Mohr <andi@lisas.de> writes:
>> Hi,
>>
>> I just had a not so nice experience
>> when finally upgrading to a new 4.1-rc5
>> with CONFIG_MODULE_COMPRESS newly enabled -
>> userspace binary parts (kmod 18 or 20 in my case)
>> did not have compression enabled
>> (at least on Debian 8pre, vs. encountering it enabled on FC21)
>> since it does not seem to be
>> the default build configuration of kmod (yet?).
>
> Sure. Let's get the maintainers to insert the actual version required
> in the help text though.
I'm not a maintainer of kmod, but the text should probably end with "If
unsure, say N."
Michal
next prev parent reply other threads:[~2015-06-03 12:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 15:29 [PATCH] modules: CONFIG_MODULE_COMPRESS: add hint that userspace support may easily be missing Andreas Mohr
2015-06-01 6:26 ` Rusty Russell
2015-06-03 12:04 ` Michal Marek [this message]
2015-06-03 17:30 ` Lucas De Marchi
2015-06-03 17:36 ` Kay Sievers
2015-06-03 17:51 ` Lucas De Marchi
2015-06-04 1:30 ` Rusty Russell
2015-06-04 2:31 ` Lucas De Marchi
2015-06-04 19:53 ` Andreas Mohr
2015-06-04 20:22 ` Rusty Russell
2015-06-07 6:18 ` Lucas De Marchi
2015-06-04 2:51 ` Marco d'Itri
2015-06-04 3:19 ` Stephen Rothwell
2015-06-04 20:09 ` Andreas Mohr
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=556EED48.6010804@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=andi@lisas.de \
--cc=beber@meleeweb.net \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=md@linux.it \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).