From: Frank Seidel <fseidel@suse.de>
To: "Uwe Kleine-König" <ukleinek@strlen.de>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, khali@linux-fr.org,
ben-linux@fluff.org, linux-i2c@vger.kernel.org,
frank@f-seidel.de, w.sang@pengutronix.de,
"David S. Miller" <davem@davemloft.net>,
Frans Pop <elendil@planet.nl>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: Re: [PATCH] i2c: add missing KERN_* constants to printks
Date: Fri, 06 Feb 2009 20:59:44 +0100 [thread overview]
Message-ID: <498C96B0.7050408@suse.de> (raw)
In-Reply-To: <20090206183542.GB6361@strlen.de>
Uwe Kleine-König schrieb:
> Are you sure about KERN_WARNING? I havn't looked deeper, but DEB2
> suggests KERN_DEBUG? What about fixing DEB[1-3] directly instead of
> each "call". e.g.
No, in this case the DEB* macro was already in many places used
with KERN_* constants just like direct printk. I didn't wanna
change that.
KERN_WARNING is just the standard/default loglevel so that this
change doesn't introduce different behaviour.
Thanks,
Frank
next prev parent reply other threads:[~2009-02-06 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 13:45 [PATCH] i2c: add missing KERN_* constants to printks Frank Seidel
2009-02-06 18:35 ` Uwe Kleine-König
2009-02-06 19:59 ` Frank Seidel [this message]
2009-02-06 20:53 ` Uwe Kleine-König
2009-02-06 21:23 ` Jean Delvare
2009-02-07 10:37 ` Frank Seidel
2009-02-07 10:52 ` Uwe Kleine-König
2009-02-07 15:58 ` Jean Delvare
2009-02-07 23:05 ` Jean Delvare
2009-02-08 13:11 ` Frank Seidel
2009-02-08 13:47 ` Jean Delvare
2009-02-08 14:16 ` Frank Seidel
2009-02-09 8:35 ` Wolfram Sang
2009-02-09 10:27 ` Jean Delvare
2009-02-08 14:18 ` [PATCHv2 1/2] " Frank Seidel
2009-02-08 14:20 ` [PATCHv2 2/2] i2c: adapt debug macros for KERN_* constants Frank Seidel
2009-02-09 15:16 ` Jean Delvare
2009-02-10 15:16 ` Wolfram Sang
2009-02-21 12:39 ` Wolfram Sang
2009-02-09 12:22 ` [PATCHv2 1/2] i2c: add missing KERN_* constants to printks Jean Delvare
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=498C96B0.7050408@suse.de \
--to=fseidel@suse.de \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=davem@davemloft.net \
--cc=elendil@planet.nl \
--cc=frank@f-seidel.de \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ukleinek@strlen.de \
--cc=w.sang@pengutronix.de \
/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).