From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 1/4] rt2x00: print warning, notice and info as default
Date: Sun, 03 Feb 2013 00:50:24 +0100 [thread overview]
Message-ID: <510DA640.6000405@gmail.com> (raw)
In-Reply-To: <20130124205931.GB16252@localhost.localdomain>
On 01/24/2013 09:59 PM, Stanislaw Gruszka wrote:
> Some messages provide useful information, but are disabled without
> CONFIG_RT2X00_DEBUG=y, so enable them by default
>
> Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
> ---
> drivers/net/wireless/rt2x00/rt2x00.h | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2x00.h b/drivers/net/wireless/rt2x00/rt2x00.h
> index 3e37c19..8ef11b6 100644
> --- a/drivers/net/wireless/rt2x00/rt2x00.h
> +++ b/drivers/net/wireless/rt2x00/rt2x00.h
> @@ -88,11 +88,11 @@
> #define ERROR_PROBE(__msg, __args...) \
> DEBUG_PRINTK_PROBE(KERN_ERR, "Error", __msg, ##__args)
> #define WARNING(__dev, __msg, __args...) \
> - DEBUG_PRINTK(__dev, KERN_WARNING, "Warning", __msg, ##__args)
> + DEBUG_PRINTK_MSG(__dev, KERN_WARNING, "Warning", __msg, ##__args)
> #define NOTICE(__dev, __msg, __args...) \
> - DEBUG_PRINTK(__dev, KERN_NOTICE, "Notice", __msg, ##__args)
> + DEBUG_PRINTK_MSG(__dev, KERN_NOTICE, "Notice", __msg, ##__args)
> #define INFO(__dev, __msg, __args...) \
> - DEBUG_PRINTK(__dev, KERN_INFO, "Info", __msg, ##__args)
> + DEBUG_PRINTK_MSG(__dev, KERN_INFO, "Info", __msg, ##__args)
> #define DEBUG(__dev, __msg, __args...) \
> DEBUG_PRINTK(__dev, KERN_DEBUG, "Debug", __msg, ##__args)
> #define EEPROM(__dev, __msg, __args...) \
This patch was applied twice. The old one and this version.
See:
28f2bce9f8bbf704c86f8c684337f82c51592c81
def64521572d8330bfa6d855e278507100fdf180
next prev parent reply other threads:[~2013-02-02 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 20:59 [PATCH 1/4] rt2x00: print warning, notice and info as default Stanislaw Gruszka
2013-01-24 21:00 ` [PATCH 2/4] rt2x00: remove NOTICE Stanislaw Gruszka
2013-01-24 21:01 ` [PATCH 3/4] rt2800usb: move "TX status missed" messages to debug level Stanislaw Gruszka
2013-01-24 21:01 ` [PATCH 4/4] rt2x00: print queue parameters at " Stanislaw Gruszka
2013-01-24 21:07 ` Gertjan van Wingerde
2013-01-26 17:16 ` Ivo Van Doorn
2013-01-24 21:07 ` [PATCH 3/4] rt2800usb: move "TX status missed" messages to " Gertjan van Wingerde
2013-01-26 17:15 ` Ivo Van Doorn
2013-01-24 21:06 ` [PATCH 2/4] rt2x00: remove NOTICE Gertjan van Wingerde
2013-01-25 12:28 ` Ivo Van Doorn
2013-01-26 17:09 ` Stanislaw Gruszka
2013-01-26 17:13 ` [PATCH 2/4 v2] " Stanislaw Gruszka
2013-01-26 17:14 ` Ivo Van Doorn
2013-01-24 21:06 ` [PATCH 1/4] rt2x00: print warning, notice and info as default Gertjan van Wingerde
2013-01-25 8:46 ` Helmut Schaa
2013-01-25 8:51 ` Gertjan van Wingerde
2013-01-25 8:52 ` Helmut Schaa
2013-02-02 23:50 ` Xose Vazquez Perez [this message]
2013-02-02 23:53 ` Xose Vazquez Perez
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=510DA640.6000405@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stf_xl@wp.pl \
--cc=users@rt2x00.serialmonkey.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;
as well as URLs for NNTP newsgroup(s).