From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: rusty@rustcorp.com.au
Subject: Re: [PATCH] Add a MODULE_VERSION macro
Date: Fri, 27 Feb 2004 18:38:58 +0200 [thread overview]
Message-ID: <CA71EA605D@vcnet.vc.cvut.cz> (raw)
On 27 Feb 04 at 6:51, Linux Kernel Mailing List wrote:
> ChangeSet 1.1713, 2004/02/26 22:51:58-08:00, akpm@osdl.org
>
> [PATCH] Add a MODULE_VERSION macro
...
> diff -Nru a/scripts/Makefile.modpost b/scripts/Makefile.modpost
> --- a/scripts/Makefile.modpost Thu Feb 26 23:11:35 2004
> +++ b/scripts/Makefile.modpost Thu Feb 26 23:11:35 2004
> @@ -10,10 +10,11 @@
...
>
> ifneq ($(filter-out $(modules),$(__modules)),)
> + $(warning Trouble: $(__modules) )
> $(warning *** Uh-oh, you have stale module entries. You messed with SUBDIRS,)
> $(warning do not complain if something goes wrong.)
> endif
Hi Rusty,
what is this line supposed to do, except making it impossible
to build kernel modules in temporary directories? Now when I build
out-of-tree modules, I get 'Trouble:' followed by approximate 16000
characters listing paths to all modules I have in kernel, for no
apparent reason (I know that I removed some module I built in /tmp...
why kernel should care, that module is gone forever), so it makes
all warning & error messages completely lost 5 screens away.
Can you remove this 'Trouble:' message, or at least provide some
way to disable that message (and two warnings below it too, they
serve no useful purpose AFAICT, as they trigger whenever you'll remove
some module from directory where you built it) ? Or at least make it
useful: print only modules which are missing, not all modules.
Thanks,
Petr Vandrovec
next reply other threads:[~2004-02-27 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 16:38 Petr Vandrovec [this message]
2004-03-01 5:41 ` [PATCH] Add a MODULE_VERSION macro Rusty Russell
2004-03-01 12:02 ` Petr Vandrovec
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=CA71EA605D@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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