From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pz0-f42.google.com ([209.85.210.42]:40007 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753790Ab1HZIzR convert rfc822-to-8bit (ORCPT ); Fri, 26 Aug 2011 04:55:17 -0400 MIME-Version: 1.0 In-Reply-To: <927eab8b5c950c13991911cd4c16457a5d618bc7.1314252671.git.joe@perches.com> References: <927eab8b5c950c13991911cd4c16457a5d618bc7.1314252671.git.joe@perches.com> Date: Fri, 26 Aug 2011 10:55:17 +0200 Message-ID: (sfid-20110826_105540_219048_2647801F) Subject: Re: [PATCH] staging: brcmfmac: Consolidate debugging macros From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: Joe Perches Cc: Henry Ptasinski , linux-kernel@vger.kernel.org, Brett Rudley , Arend Van Spriel , Roland Vossen , "Franky (Zhenhui) Lin" , devel@linuxdriverproject.org, Greg KH , Kan Yan , linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 2011/8/25 Joe Perches : > Convert multiple BRCMF_ macros to a single > brcmf_dbg(level, fmt, ...) macro. I'm not sure if that "_dbg" suffix is a really good choice. You use "_dbg" for all the kinds of messages, while "DEBUG" is already one kind of messages. We have also other types like EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO and DEBUG. You choice makes it messy according to me. Wouldn't something like brcmf_print be much better choice? I really don't like such a mixing dbg&DEBUG, dbd&ERR, etc. -- RafaƂ