From: Leon Gross <leon.gross@rub.de>
To: Greg KH <greg@kroah.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: List of all available kernel modules per version
Date: Thu, 23 Sep 2021 19:55:45 +0200 [thread overview]
Message-ID: <8d55ef0a-32bf-6a4d-e742-ad78e5825598@rub.de> (raw)
In-Reply-To: <YUy7hecA+eAxrAxD@kroah.com>
> A:http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
Alright, nice annotation, thanks.
> But how are you mapping a module "name" to what it does?
modprobe [modulename] , i thought that was how a module is mapped to a
name? Or do you mean something different?
> Why does that matter?
It matters because if I have a problem to solve and I know the kernel
module that is required to do that (like nvme_tcp) then I can narrow
down which kernel to use.
> Do a 'make allmodconfig' build for every major release and sort the
> output. Should be pretty easy to script if you really need this.
That sounds like a way to go.
Thanks alot for your help!
Leon
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-23 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:39 List of all available kernel modules per version Leon Gross
2021-09-23 16:57 ` Greg KH
2021-09-23 17:32 ` Leon Gross
2021-09-23 17:38 ` Greg KH
2021-09-23 17:55 ` Leon Gross [this message]
2021-09-23 18:12 ` Greg KH
2021-09-23 22:04 ` Valdis Klētnieks
2021-09-25 0:08 ` jim.cromie
2021-09-25 3:32 ` Valdis Klētnieks
2021-09-25 3:35 ` Valdis Klētnieks
2021-09-26 18:00 ` jim.cromie
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=8d55ef0a-32bf-6a4d-e742-ad78e5825598@rub.de \
--to=leon.gross@rub.de \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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