From: Sebastien.Hinderer@ens-lyon.org (Sébastien Hinderer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Message not appearing in mesg
Date: Tue, 7 Jul 2015 17:11:36 +0200 [thread overview]
Message-ID: <20150707151136.GA9917@pema> (raw)
In-Reply-To: <CAPA4HGVDe_nx_X0Q7V1MMx=-jpBGWwZDc25P8tN54m3Db+RuDg@mail.gmail.com>
Hi Luis,
Many thanks for your prompt and helpfulresponse!
> Do you have the relevant DEBUG macros activated in your kernel's
> configuration?
Perhaps not...
> https://www.kernel.org/doc/local/pr_debug.txt
Read this, thanks. But that has nothing to do with KConfigmacros, has
it?
> http://elinux.org/Debugging_by_printing
>
> If not, activate them. Or if in a pinch, switch to using pr_alert() for
> development.
What surprises me is that I made sue the message appears inthe .ko file
and it was there,whereas it seems pr_debug discards its argument at
compile time. Or is it at execution time?
Thanks!
S?bastien.
next prev parent reply other threads:[~2015-07-07 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:53 Message not appearing in mesg Sébastien Hinderer
2015-07-07 15:02 ` Luis de Bethencourt
2015-07-07 15:11 ` Sébastien Hinderer [this message]
2015-07-07 15:43 ` Luis de Bethencourt
2015-07-07 16:34 ` Shérab
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=20150707151136.GA9917@pema \
--to=sebastien.hinderer@ens-lyon.org \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).