From: Valdis.Kletnieks@vt.edu
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Paulo Marques <pmarques@grupopie.com>
Subject: Re: [PATCH 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile
Date: Mon, 04 Apr 2011 08:45:58 -0400 [thread overview]
Message-ID: <131611.1301921158@localhost> (raw)
In-Reply-To: Your message of "Mon, 04 Apr 2011 13:40:51 +0300." <1301913651-9055-2-git-send-email-dedekind1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Mon, 04 Apr 2011 13:40:51 +0300, Artem Bityutskiy said:
> 3. By default KALLSYMS_EXTRA_PASS is disabled and if kallsyms has issues,
> "make" should print a warning and suggest using KALLSYMS_EXTRA_PASS
If the Makefile has enough information to print the warning, why can't it go
ahead and do the extra pass itself instead of issuing the warning?
(I'm obviously missing something here, as I'm foolishly posting to lkml before
caffeine ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-04-04 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 10:40 [PATCH 1/2] Kconfig: improve KALLSYMS_ALL documentation Artem Bityutskiy
2011-04-04 10:40 ` [PATCH 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile Artem Bityutskiy
2011-04-04 12:17 ` Michal Marek
2011-04-04 12:48 ` Artem Bityutskiy
2011-04-04 12:45 ` Valdis.Kletnieks [this message]
2011-04-04 12:47 ` Artem Bityutskiy
2011-04-04 15:22 ` Valdis.Kletnieks
2011-04-04 15:37 ` Artem Bityutskiy
2011-04-04 16:01 ` Paulo Marques
2011-04-04 15:47 ` Artem Bityutskiy
2011-04-04 16:22 ` [PATCH 1/2] Kconfig: improve KALLSYMS_ALL documentation Randy Dunlap
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=131611.1301921158@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=dedekind1@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pmarques@grupopie.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