public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Leon Gross <leon.gross@rub.de>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: List of all available kernel modules per version
Date: Thu, 23 Sep 2021 19:38:13 +0200	[thread overview]
Message-ID: <YUy7hecA+eAxrAxD@kroah.com> (raw)
In-Reply-To: <6e8d1582-f01e-65da-ffce-70ce0d43a98b@rub.de>

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

On Thu, Sep 23, 2021 at 07:32:40PM +0200, Leon Gross wrote:
> The first thing I am interested in a complete list of all kernel modules of
> the x86 plattform for any kernel version.

Which x86 platform?  There are many different ones.

> The problem I want to solve is a generalized way to find out the kernel
> versions in which modules first were supported.

But how are you mapping a module "name" to what it does?

Why does that matter?

> One exmaple is the `nvme_tcp` module. Trough testing on machines running
> different kernels and stackoverflow articles
> I figured out that it might have been supported since kernel version 5.x. I
> would like to have a way to verfiy such kind of
> information for any given module.

Do a 'make allmodconfig' build for every major release and sort the
output.  Should be pretty easy to script if you really need this.

Good luck!

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-09-23 17:40 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 [this message]
2021-09-23 17:55       ` Leon Gross
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=YUy7hecA+eAxrAxD@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=leon.gross@rub.de \
    /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