[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALyZvKzDYUFxbkZW=zVP6Z5KV3QQGJaZb6uW35qkZRV2xYUzJg@mail.gmail.com>
Date: Thu, 10 May 2018 12:03:01 +0000
From: Jason Vas Dias <jason.vas.dias@...il.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Lucas De Marchi <lucas.de.marchi@...il.com>,
Harish Jenny K N <harish_kandiga@...tor.com>,
linux-modules <linux-modules@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
greg KH <gregkh@...uxfoundation.org>
Subject: Re: Differences between builtins and modules
Sorry I didn't see this mail until now - RE:
Randy Dunlap <rdunlap@...radead.org> wrote:
> Would someone please answer/reply to this (related) kernel bugzilla entry:
> https://bugzilla.kernel.org/show_bug.cgi?id=118661
Yes, I raised this bug because I think modinfo should return 0 exit status
if a requested module is built-in, not just when it has been loaded, like
this modified version does:
$ modinfo snd
modinfo: ERROR: Module snd not found.
built-in: snd
$ echo $?
0
What was the query about the Bug 118661 that needs to be answered ?
I don't see any query on the bug report - just a comment from someone
who also agrees modinfo should return OK for a built-in module .
Glad to hear someone is finally considering fixing modinfo to report
status of built-in modules - with only a 2 year response time.
Thanks & Best Regards,
Jason
Powered by blists - more mailing lists