From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <4502a7e5-930f-15b6-fbef-929df29d5ef0@infradead.org> References: <54EB4C83.2000500@suse.cz> <4502a7e5-930f-15b6-fbef-929df29d5ef0@infradead.org> From: Jason Vas Dias Date: Thu, 10 May 2018 12:03:01 +0000 Message-ID: Subject: Re: Differences between builtins and modules To: Randy Dunlap Cc: Lucas De Marchi , Harish Jenny K N , linux-modules , lkml , greg KH Content-Type: text/plain; charset="UTF-8" List-ID: Sorry I didn't see this mail until now - RE: Randy Dunlap 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