linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joe Perches <joe@perches.com>
Cc: Henry Ptasinski <henryp@broadcom.com>,
	linux-kernel@vger.kernel.org, Brett Rudley <brudley@broadcom.com>,
	Arend Van Spriel <arend@broadcom.com>,
	Roland Vossen <rvossen@broadcom.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	devel@linuxdriverproject.org, Greg KH <gregkh@suse.de>,
	Kan Yan <kanyan@broadcom.com>,
	linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: brcmfmac: Consolidate debugging macros
Date: Thu, 25 Aug 2011 08:47:05 -0700	[thread overview]
Message-ID: <20110825154705.GA6567@kroah.com> (raw)
In-Reply-To: <927eab8b5c950c13991911cd4c16457a5d618bc7.1314252671.git.joe@perches.com>

On Wed, Aug 24, 2011 at 11:16:48PM -0700, Joe Perches wrote:
> Convert multiple BRCMF_<debug_level> macros to a single
> brcmf_dbg(level, fmt, ...) macro.
> 
> Remove the now unnecessary double parentheses in the uses
> of the old macros when converting to brcmf_dbg.
> 
> Delete all uses of "%s: [fmt]", __func__, args... and move
> the "%s: ", __func__ to the macro for consistency.
> 
> Coalesce long formats.
> 
> Signed-off-by: Joe Perches <joe@perches.com>

Applied, thanks.

greg k-h

  reply	other threads:[~2011-08-25 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  6:16 [PATCH] staging: brcmfmac: Consolidate debugging macros Joe Perches
2011-08-25 15:47 ` Greg KH [this message]
2011-08-26  8:57   ` Rafał Miłecki
2011-08-26  9:05     ` Joe Perches
2011-08-26  8:55 ` Rafał Miłecki
2011-08-26  9:02   ` Joe Perches
2011-08-26  9:19     ` Rafał Miłecki
2011-08-26  9:24       ` Arend van Spriel
2011-08-27  7:29         ` Rafał Miłecki

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=20110825154705.GA6567@kroah.com \
    --to=greg@kroah.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devel@linuxdriverproject.org \
    --cc=frankyl@broadcom.com \
    --cc=gregkh@suse.de \
    --cc=henryp@broadcom.com \
    --cc=joe@perches.com \
    --cc=kanyan@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.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).