From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Emil Medve <Emilian.Medve@Freescale.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
i2c@lm-sensors.org, linux-omap-open-source@linux.omap.com,
Emil Medve <Emilian.Medve@Freescale.com>
Subject: Re: [PATCH] Move the definition of pr_err() into kernel.h
Date: Wed, 12 Sep 2007 12:59:15 +0200 [thread overview]
Message-ID: <20070912125915.5b5d8aa5@oldman> (raw)
In-Reply-To: <11895225651521-git-send-email-Emilian.Medve@Freescale.com>
On Tue, 11 Sep 2007 09:56:05 -0500
Emil Medve <Emilian.Medve@Freescale.com> wrote:
> Other pr_*() macros are already defined in kernel.h, but pr_err() was defined
> multiple times in several other places
>
> Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
pr_error seems better than pr_err
Please add the full set:
pr_alert
pr_critical
pr_error
pr_warn
pr_notice
next prev parent reply other threads:[~2007-09-12 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 14:56 [PATCH] Move the definition of pr_err() into kernel.h Emil Medve
2007-09-11 15:41 ` Randy Dunlap
2007-09-12 10:59 ` Stephen Hemminger [this message]
2007-09-15 8:57 ` Jan Engelhardt
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=20070912125915.5b5d8aa5@oldman \
--to=shemminger@linux-foundation.org \
--cc=Emilian.Medve@Freescale.com \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=netdev@vger.kernel.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).