From: Karel Zak <kzak@redhat.com>
To: Alexey Gladkov <gladkov.alexey@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Add modules.builtin.modinfo support
Date: Fri, 11 Oct 2019 08:58:42 +0200 [thread overview]
Message-ID: <20191011065842.f5tm6ynkbltiqcyq@10.255.255.10> (raw)
In-Reply-To: <20191010120928.3817287-1-gladkov.alexey@gmail.com>
Alexey, it seems you need another mailing list for libkmod, see:
https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/about/
Thanks,
Karel
> Alexey Gladkov (4):
> libkmod: Add parser for modules.builtin.modinfo
> libkmod: Add function to get list of built-in modules
> Lookup aliases in the modules.builtin.modinfo
> modinfo: Show information about built-in modules
>
> Makefile.am | 1 +
> libkmod/libkmod-builtin.c | 231 +++++++++++++++++++++++++++++++++++++
> libkmod/libkmod-internal.h | 10 ++
> libkmod/libkmod-module.c | 76 ++++++++++--
> libkmod/libkmod.c | 25 ++++
> libkmod/libkmod.h | 1 +
> tools/depmod.c | 63 ++++++++++
> tools/modinfo.c | 39 ++++---
> 8 files changed, 419 insertions(+), 27 deletions(-)
> create mode 100644 libkmod/libkmod-builtin.c
>
> --
> 2.21.0
>
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2019-10-11 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:09 [PATCH v1 0/4] Add modules.builtin.modinfo support Alexey Gladkov
2019-10-10 12:09 ` [PATCH v1 1/4] libkmod: Add parser for modules.builtin.modinfo Alexey Gladkov
2019-10-10 12:09 ` [PATCH v1 2/4] libkmod: Add function to get list of built-in modules Alexey Gladkov
2019-10-10 12:09 ` [PATCH v1 3/4] Lookup aliases in the modules.builtin.modinfo Alexey Gladkov
2019-10-10 12:09 ` [PATCH v1 4/4] modinfo: Show information about built-in modules Alexey Gladkov
2019-10-11 6:58 ` Karel Zak [this message]
2019-10-11 8:17 ` [PATCH v1 0/4] Add modules.builtin.modinfo support Alexey Gladkov
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=20191011065842.f5tm6ynkbltiqcyq@10.255.255.10 \
--to=kzak@redhat.com \
--cc=gladkov.alexey@gmail.com \
--cc=util-linux@vger.kernel.org \
/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).