linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	dsterba@suse.cz, Masahiro Yamada <masahiroy@kernel.org>,
	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 16:48:43 +0100	[thread overview]
Message-ID: <06491eb2-b43c-badc-ce3c-7709abe06a3f@metux.net> (raw)
In-Reply-To: <20191205032503.GA3981@debian>

On 05.12.19 04:25, Bhaskar Chowdhury wrote:

Hi,

> The whole point behind this is to give the developers a convenient point
> without going through all the rigorous details.

I see your point, but I wonder whether it maybe better should go
into kmod.

--mtx

---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

      parent reply	other threads:[~2019-12-06 15:49 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
2019-12-06 15:48       ` Enrico Weigelt, metux IT consult [this message]

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=06491eb2-b43c-badc-ce3c-7709abe06a3f@metux.net \
    --to=lkml@metux.net \
    --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 \
    --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;
as well as URLs for NNTP newsgroup(s).