From: Dan Mick <dan.mick@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Alex Elder <elder@inktank.com>, Gregory Farnum <greg@inktank.com>,
jie sun <0maidou0@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re:
Date: Thu, 25 Oct 2012 14:28:07 -0700 [thread overview]
Message-ID: <5089AEE7.2010302@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210250838070.25762@cobra.newdream.net>
>> static void ceph_fault(struct ceph_connection *con)
>> __releases(con->mutex)
>> {
>> pr_err("%s%lld %s %s\n", ENTITY_NAME(con->peer_name),
>> ceph_pr_addr(&con->peer_addr.in_addr), con->error_msg)
>>
>> Perhaps this should become pr_info() or something. Sage?
>
> Yeah, I think pr_info() is probably the right choice. Do you know if that
> hits the console by default, or just dmesg/kern.log?
pr_info is level 6, KERN_INFO; by default, /proc/sys/kernel/printk has
4 4 1 7 in it, the first 4 of which means 4-and-lower go to console. So
debug, info, notice messages all are options for "not console".
next prev parent reply other threads:[~2012-10-25 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 4:12 (unknown), jie sun
2012-10-23 11:50 ` Wido den Hollander
2012-10-24 5:48 ` Re: jie sun
2012-10-24 5:58 ` Re: Gregory Farnum
[not found] ` <CAB6Jr7SbbAE=yEVgg+UupTmavKfvFvGj8j7C9M0Ya2FocNmw9w@mail.gmail.com>
2012-10-25 12:15 ` Re: Gregory Farnum
2012-10-25 14:36 ` Re: Alex Elder
2012-10-25 15:38 ` Re: Sage Weil
2012-10-25 21:28 ` Dan Mick [this message]
2012-10-25 22:15 ` Re: Alex Elder
2012-10-26 3:08 ` Re: jie sun
-- strict thread matches above, loose matches on Subject: below --
2020-03-27 9:20 (unknown) chenanqing
[not found] ` <5e7dc543.vYG3wru8B/me1sOV%chenanqing-Oq79sGaMObY@public.gmane.org>
2020-03-27 15:53 ` Lee Duncan
2020-03-27 8:36 (unknown) chenanqing
2020-03-27 8:59 ` Ilya Dryomov
2017-11-13 15:04 Re: Amos Kalonzo
2017-05-03 11:26 Re: Paul Lopez-Bravo
2015-11-01 20:03 Mario, Franco
2015-08-11 10:57 RE: zso2bytom
2013-08-23 6:18 info
[not found] <4FD71854.6060503@hastexo.com>
2012-06-12 10:44 ` "Radosgw installation and administration" docs Florian Haas
2012-06-12 16:47 ` Yehuda Sadeh
2012-06-12 18:11 ` Florian Haas
2012-06-12 18:54 ` Yehuda Sadeh
2012-07-01 20:22 ` Chuanyu
2012-07-02 9:35 ` Chuanyu Tsai
2012-05-08 0:54 (unknown), Tim Flavin
2012-05-17 21:10 ` Josh Durgin
2011-08-15 23:01 Re: jeffrice
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=5089AEE7.2010302@inktank.com \
--to=dan.mick@inktank.com \
--cc=0maidou0@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.com \
--cc=greg@inktank.com \
--cc=sage@inktank.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