All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: dsterba@suse.cz, 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: Fri, 6 Dec 2019 13:40:27 +0530	[thread overview]
Message-ID: <20191206081027.GA1165@ArchLinux> (raw)
In-Reply-To: <CAK7LNARdOGfvc_8TMX+KbJQ1DRGy8_xZsdDye1ZrvimSS1VoFQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2540 bytes --]

On 01:08 Fri 06 Dec 2019, Masahiro Yamada wrote:
>   On Thu, Dec 5, 2019 at 12:25 PM Bhaskar Chowdhury
>   <[1]unixbhaskar@gmail.com> wrote:
>
>     On 16:07 Wed 04 Dec 2019, David Sterba wrote:
>     >On Wed, Dec 04, 2019 at 12:10:25PM +0900, Masahiro Yamada wrote:
>     >> On Tue, Dec 3, 2019 at 6:49 PM Bhaskar Chowdhury
>     <[2]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.
>     lsmod and modinfo already are pretty verbose and the one liner is
>     using
>     one of them to cut thing out of it....can you give it another
>     look???
>     Moreover,this is sort and precise and can be parsed by other
>     scripts.
>     The whole point behind this is to give the developers a convenient
>     point
>     without going through all the rigorous details.
>
>   lsmod and modinfo are good.
>   If you are not satisfied with the current format,
>   talk to the kmod maintainer.
>   As a maintainer, I need to avoid the situation
>   where upstream tree is flooded with weird scripts like this.
>   One more thing:
>   Despite advice from Randy over again,
>   you are still not able to submit a patch correctly.
>   (see what you sent as v2).
>   Do not get me wrong. I am not saying you to send v3.
>   I do not like this patch. Please stop.
>   --
I completely get you. I should stop sending this. Thanks for the heads
up. 

And I was not denying the verbosity of lsmod and modinfo , as I was
pointing out to someone else.

About the V2, this was a mistake , I know once I saw it alas! after
sending it you. So, my apology. 

One thing get it straight , I am NOT trying to flooding with some airy
fairy script , I know what it takes to maintain that bloody thing.

Your time is precious like mine, never try to gobbles it by sending
garbage.

I was thinking make it easy for others, not sure why you think it's
wired.

Again , thanks for the heads up...above statements are STRICTLY NOT in my
defence not to cover the mistake.

>   Best Regards
>   Masahiro Yamada
>
>References
>
>   1. mailto:unixbhaskar@gmail.com
>   2. mailto:unixbhaskar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-12-06  8:10 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
2019-12-05  3:25     ` Bhaskar Chowdhury
     [not found]       ` <CAK7LNARdOGfvc_8TMX+KbJQ1DRGy8_xZsdDye1ZrvimSS1VoFQ@mail.gmail.com>
2019-12-06  8:10         ` Bhaskar Chowdhury [this message]
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=20191206081027.GA1165@ArchLinux \
    --to=unixbhaskar@gmail.com \
    --cc=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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.