From: David Sterba <dsterba@suse.cz>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
Michal Marek <michal.lkml@markovi.net>,
Randy Dunlap <rdunlap@infradead.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Enlist running kernel modules information
Date: Wed, 4 Dec 2019 16:07:30 +0100 [thread overview]
Message-ID: <20191204150728.GD2734@twin.jikos.cz> (raw)
In-Reply-To: <CAK7LNASyrYv+pufwe4CfiNvd7NtriLw=FRdLOtu7CrbmZDSVHg@mail.gmail.com>
On Wed, Dec 04, 2019 at 12:10:25PM +0900, Masahiro Yamada wrote:
> On Tue, Dec 3, 2019 at 6:49 PM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> > +awk '{print $1}' "/proc/modules" | xargs modinfo | awk '/^(filename|desc|depends)/'
>
> I want to see a good reason (e.g. useful for other developers) for upstreaming.
> This script looks like your custom script, which you can maintain locally.
I think the verbosity should be added to either lsmod or modinfo, not
some script in kernel git.
next prev parent reply other threads:[~2019-12-04 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 9:48 [PATCH 1/2] Enlist running kernel modules information Bhaskar Chowdhury
2019-12-04 3:10 ` Masahiro Yamada
2019-12-04 4:22 ` Bhaskar Chowdhury
2019-12-04 13:48 ` Enrico Weigelt, metux IT consult
2019-12-05 3:30 ` Bhaskar Chowdhury
2019-12-04 15:07 ` David Sterba [this message]
2019-12-05 3:25 ` Bhaskar Chowdhury
[not found] ` <CAK7LNARdOGfvc_8TMX+KbJQ1DRGy8_xZsdDye1ZrvimSS1VoFQ@mail.gmail.com>
2019-12-06 8:10 ` Bhaskar Chowdhury
2019-12-06 15:48 ` Enrico Weigelt, metux IT consult
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=20191204150728.GD2734@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.com \
/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