From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: linux-modules <linux-modules@vger.kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] kmod 22
Date: Tue, 17 Nov 2015 22:22:49 -0200 [thread overview]
Message-ID: <CAKi4VA+YGLYr_yciXOnwsACd69CZ+R86SsZr4eAWe-3KEJcpaA@mail.gmail.com> (raw)
kmod 22 is out:
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-22.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-22.tar.sign
Tiny release:
- Tools:
- Change defaul log level for tools to WARNING rather than
ERROR and update
some log levels for current messages
- depmod doesn't fallback to uname if a bad version is passed
in the command
line anymore. We just exit with an error.
- insmod was taught the -f flag, just like in modprobe. It was
previously
silently ignoring it.
- libkmod
- New kmod_get_dirname() API to get the module directory set in the
context
- Bug fixes:
- Fix return code in error path of kmod_module_insert_module(). We were
previously returning ENOSYS rather than ENOENT.
Shortlog:
Laura Abbott (5):
README: Indicate cython requirements
modprobe: Update error message when path is missing
Change default log level
depmod: Remove unprinted debug messages
depmod: Don't fall back to uname on bad version
Lucas De Marchi (4):
Add README.md file with build details
libkmod-module: fix return code in error path
libkmod: export new kmod_get_dirname() function
kmod 22
Natanael Copa (1):
build: let sed use posix ERE instead of GNU extension
Philippe De Swert (1):
insmod: do support -f
Lucas De Marchi
reply other threads:[~2015-11-18 0:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAKi4VA+YGLYr_yciXOnwsACd69CZ+R86SsZr4eAWe-3KEJcpaA@mail.gmail.com \
--to=lucas.de.marchi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--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).