From: Greg KH <greg@kroah.com>
To: Andy Nicholas <andy.nicholas@shield.ai>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Finding all modules which consume kernel lib?
Date: Sat, 9 Mar 2019 09:29:04 +0100 [thread overview]
Message-ID: <20190309082904.GA12998@kroah.com> (raw)
In-Reply-To: <CAH_BzbLiTk4tXnQiBan0RnqFtGU-rzpBx1OqYZ4GC0n8ni5DOw@mail.gmail.com>
On Sat, Mar 09, 2019 at 12:07:00AM -0800, Andy Nicholas wrote:
> Hello,
>
> Is there a website or service or tool or package or script or something
> which allows me to determine which pieces of the compiled kernel
> (especially modules) contained the source-code changes I might make to any
> given directory? Like a kernel-code dependency graph website?
>
> For instance, assume I made a change to code in net/wireless/. How do I
> figure out which pieces of the kernel or modules get linked against the
> library built from this directory?
>
> I could attempt to trace the kernel's build output line-by-line and then
> grep through the output looking for which other code is linking against
> cfg80211. That is way too tedious. In this case I would like to know which
> kernel modules I would need to, potentially, re-test because I apply a
> patch to this directory.... without examining the build logs.
Just look at the build logs, it will show you exactly what gets rebuilt
when you touch a single file (or multiple files.) That's the simplest
way to do what you want here.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-09 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 8:07 Finding all modules which consume kernel lib? Andy Nicholas
2019-03-09 8:29 ` Greg KH [this message]
2019-03-09 10:04 ` Lev Olshvang
2019-03-09 17:00 ` valdis.kletnieks
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=20190309082904.GA12998@kroah.com \
--to=greg@kroah.com \
--cc=andy.nicholas@shield.ai \
--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;
as well as URLs for NNTP newsgroup(s).