From: Joe Perches <joe@perches.com>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: linux-wireless@vger.kernel.org, wcn36xx@lists.infradead.org
Subject: Re: [PATCH 13/16] wcn36xx: Add wcn36xx.h
Date: Tue, 20 Aug 2013 11:04:50 -0700 [thread overview]
Message-ID: <1377021890.2016.55.camel@joe-AO722> (raw)
In-Reply-To: <1377020479-16935-14-git-send-email-k.eugene.e@gmail.com>
On Tue, 2013-08-20 at 19:41 +0200, Eugene Krasnikov wrote:
> Adding wcn36xx.h
[]
> +#define DRIVER_PREFIX "wcn36xx: "
[]
I think you should use pr_fmt and/or netdev_<level>
> +#define wcn36xx_error(fmt, arg...) do { \
> + pr_err(DRIVER_PREFIX "ERROR " fmt "\n", ##arg); \
> + __WARN(); \
> +} while (0)
What value is there in this __WARN?
Please use _err rather than _error
> +#define wcn36xx_warn(fmt, arg...) \
> + pr_warn(DRIVER_PREFIX "WARNING " fmt "\n", ##arg)
> +
> +#define wcn36xx_info(fmt, arg...) \
> + pr_info(DRIVER_PREFIX fmt "\n", ##arg)
> +
> +#define wcn36xx_dbg(mask, fmt, arg...) do { \
> + if (debug_mask & mask) \
> + pr_debug(DRIVER_PREFIX fmt "\n", ##arg); \
> +} while (0)
> +
> +#define wcn36xx_dbg_dump(mask, prefix_str, buf, len) do { \
> + if (debug_mask & mask) \
> + print_hex_dump(KERN_DEBUG, prefix_str, \
> + DUMP_PREFIX_OFFSET, 32, 1, \
> + buf, len, false); \
> +} while (0)
> +
Please move the "\n" to the uses instead of the macro.
This would be consistent with all the other ath macros.
next prev parent reply other threads:[~2013-08-20 18:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 17:41 [PATCH 00/16] wcn36xx: mac80211 driver for Qualcomm WCN3660/WCN3680 hardware Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 01/16] wcn36xx: Add main.c Eugene Krasnikov
2013-08-20 20:59 ` Johannes Berg
2013-08-21 8:36 ` Eugene Krasnikov
2013-08-21 8:39 ` Johannes Berg
2013-08-21 9:00 ` Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 02/16] wcn36xx: Add debug.c Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 03/16] wcn36xx: Add debug.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 04/16] wcn36xx: Add dxe.c Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 05/16] wcn36xx: Add dxe.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 06/16] wcn36xx: Add hal.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 07/16] wcn36xx: Add pmc.c Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 08/16] wcn36xx: Add pmc.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 09/16] wcn36xx: Add smd.c Eugene Krasnikov
2013-08-20 18:12 ` Joe Perches
2013-08-21 7:58 ` Eugene Krasnikov
2013-08-21 8:15 ` Johannes Berg
2013-08-21 8:49 ` Eugene Krasnikov
2013-08-21 11:20 ` Joe Perches
2013-08-20 17:41 ` [PATCH 10/16] wcn36xx: Add smd.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 11/16] wcn36xx: Add txrx.c Eugene Krasnikov
2013-08-20 21:01 ` Johannes Berg
2013-08-21 8:39 ` Eugene Krasnikov
2013-08-20 21:03 ` Johannes Berg
2013-08-21 8:44 ` Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 12/16] wcn36xx: Add txrx.h Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 13/16] wcn36xx: Add wcn36xx.h Eugene Krasnikov
2013-08-20 18:04 ` Joe Perches [this message]
2013-08-21 7:55 ` Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 14/16] wcn36xx: Add Makefile Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 15/16] wcn36xx: Add Kconfig Eugene Krasnikov
2013-08-20 17:41 ` [PATCH 16/16] wcn36xx: Add wcn36xx to ath Makefile and Kconfig Eugene Krasnikov
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=1377021890.2016.55.camel@joe-AO722 \
--to=joe@perches.com \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wcn36xx@lists.infradead.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