From: Bertrand Jacquin <beber@meleeweb.net>
To: Rusty Russell <rusty@rustcorp.com.au>, linux-kbuild@vger.kernel.org
Cc: Bertrand Jacquin <beber@meleeweb.net>,
linux-kernel@vger.kernel.org, Willy Tarreau <w@1wt.eu>
Subject: [PATCHv2 0/3] handle module compression at install
Date: Tue, 19 Aug 2014 20:57:37 +0200 [thread overview]
Message-ID: <1408474660-24999-1-git-send-email-beber@meleeweb.net> (raw)
Hi,
Here is patchset based on commit 480cadc (v3.17-rc1-22-g480cadc) that
aims to handle kernel modules compression while running make modules_install.
Please Cc me, as I'm not subscribed to LKML.
Changes since v1:
- Drop -9 argument to gzip and xz since Andi Kleen and Rusty Russell
prove no gain is made using them.
Bertrand Jacquin (3):
modinst: wrap long lines in order to enhance cmd_modules_install
kbuild: handle module compression while running 'make
modules_install'.
modsign: lookup lines ending in .ko in .mod files
Makefile | 15 +++++++++++++++
init/Kconfig | 43 +++++++++++++++++++++++++++++++++++++++++++
scripts/Makefile.modinst | 7 ++++++-
scripts/Makefile.modsign | 2 +-
4 files changed, 65 insertions(+), 2 deletions(-)
--
2.0.4
next reply other threads:[~2014-08-19 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 18:57 Bertrand Jacquin [this message]
2014-08-19 18:57 ` [PATCH 1/3] modinst: wrap long lines in order to enhance cmd_modules_install Bertrand Jacquin
2014-08-19 22:02 ` Jim Davis
2014-08-20 16:08 ` Rusty Russell
2014-08-19 18:57 ` [PATCH 2/3] kbuild: handle module compression while running 'make modules_install' Bertrand Jacquin
2014-08-20 16:09 ` Rusty Russell
2014-10-12 15:50 ` Andev
2014-10-12 16:40 ` Willy Tarreau
2014-10-12 17:06 ` Andev
2014-08-19 18:57 ` [PATCH 3/3] modsign: lookup lines ending in .ko in .mod files Bertrand Jacquin
2014-08-20 16:06 ` Rusty Russell
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=1408474660-24999-1-git-send-email-beber@meleeweb.net \
--to=beber@meleeweb.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®