From: Joe Perches <joe@perches.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: Move pr_fmt macros to a single location
Date: Tue, 17 Jan 2012 19:12:16 -0800 [thread overview]
Message-ID: <1326856336.20922.22.camel@joe2Laptop> (raw)
In-Reply-To: <4f1636b2.D5g8MJEc04WZglzi%Larry.Finger@lwfinger.net>
On Tue, 2012-01-17 at 21:04 -0600, Larry Finger wrote:
> Although the rtlwifi family of devices contains 11 copies of the pr_fmt
> macro, the macro is not defined for all routines that need it. By moving
> the macro to wifi.h, a single copy is available for all routines.
[]
> +++ wireless-testing-new/drivers/net/wireless/rtlwifi/wifi.h
> @@ -172,6 +172,8 @@ enum hardware_type {
> _pdesc->rxmcs == DESC92_RATE5_5M || \
> _pdesc->rxmcs == DESC92_RATE11M)
>
> +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
This #define should be before any #include of kernel.h/printk.h
or any other #include that might use it indirectly.
prev parent reply other threads:[~2012-01-18 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 3:04 [PATCH] rtlwifi: Move pr_fmt macros to a single location Larry Finger
2012-01-18 3:12 ` Joe Perches [this message]
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=1326856336.20922.22.camel@joe2Laptop \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).