From: Michal Marek <mmarek@suse.cz>
To: Mike Ton <linuxham@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix bug with modpost Makefile warn flag inclusion
Date: Tue, 19 Aug 2014 09:00:50 +0200 [thread overview]
Message-ID: <53F2F622.2020908@suse.cz> (raw)
In-Reply-To: <CA+1_+FO=65Hbd1bcTgb6WS4OwdF6W38fyiE1C2rWiU+=s_CHQQ@mail.gmail.com>
On 2014-08-18 21:52, Mike Ton wrote:
> From: Michael Ton <linuxham@gmail.com <mailto:linuxham@gmail.com>>
>
> The current Makefile.modpost file includes a warn (-w) flag to modpost
> if KBUILD_EXTMOD or KBUILD_MODPOST_WARN. This flag should only be added
> if both flags are true.
Why?
> Whenever KBUILD_MODPOST is true, modpost
> currently only prints warnings and does not exit on error (such as on an
> undefined symbol).
Yes, that's what Documentation/kbuild/kbuild.txt and the comment at the
beginning of the Makefile say.
Michal
next parent reply other threads:[~2014-08-19 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+1_+FO=65Hbd1bcTgb6WS4OwdF6W38fyiE1C2rWiU+=s_CHQQ@mail.gmail.com>
2014-08-19 7:00 ` Michal Marek [this message]
2014-08-18 20:20 [PATCH] kbuild: fix bug with modpost Makefile warn flag inclusion Michael Ton
2014-08-19 4:35 ` Sam Ravnborg
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=53F2F622.2020908@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxham@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).