(Using Jason Baron's most current email address)
On Tue, 2013-06-25 at 10:56 -0700, Joe Perches wrote:
> On Tue, 2013-06-25 at 10:38 -0700, Greg KH wrote:
> > On Tue, Jun 25, 2013 at 10:29:50AM -0700, Joe Perches wrote:
> > > a long needed extension to dev_dbg is to enable classes
> > > of message
On Tue, Jun 25, 2013 at 06:49:12PM +0100, Rupesh Gujare wrote:
> On 25/06/13 18:02, Greg KH wrote:
> >On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
> >>convert all debug messages from printk to dev_dbg() & add kernel config to
> >>enable/disable these messages during compilation.
>
On Tue, 2013-06-25 at 10:38 -0700, Greg KH wrote:
> On Tue, Jun 25, 2013 at 10:29:50AM -0700, Joe Perches wrote:
> > a long needed extension to dev_dbg is to enable classes
> > of messages by level or mask.
> >
> > There are many existing macros like
> >
> > #define module_dbg(level, fmt, ...)
>
On Tue, 25 Jun 2013, Rupesh Gujare wrote:
> On 25/06/13 18:02, Greg KH wrote:
> > On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
> >> convert all debug messages from printk to dev_dbg() & add kernel config to
> >> enable/disable these messages during compilation.
> > No, just use t
On 25/06/13 18:02, Greg KH wrote:
On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
convert all debug messages from printk to dev_dbg() & add kernel config to
enable/disable these messages during compilation.
No, just use the built-in dynamic debug code in the kernel, no need to
pr
On Tue, Jun 25, 2013 at 10:29:50AM -0700, Joe Perches wrote:
> On Tue, 2013-06-25 at 10:02 -0700, Greg KH wrote:
> > On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
> > > convert all debug messages from printk to dev_dbg() & add kernel config to
> > > enable/disable these messages du
On Tue, 2013-06-25 at 10:02 -0700, Greg KH wrote:
> On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
> > convert all debug messages from printk to dev_dbg() & add kernel config to
> > enable/disable these messages during compilation.
> No, just use the built-in dynamic debug code in
On Tue, Jun 25, 2013 at 05:30:02PM +0100, Rupesh Gujare wrote:
> convert all debug messages from printk to dev_dbg() & add kernel config to
> enable/disable these messages during compilation.
No, just use the built-in dynamic debug code in the kernel, no need to
provide any new macros or functions
On Tue, 2013-06-25 at 17:30 +0100, Rupesh Gujare wrote:
> convert all debug messages from printk to dev_dbg() & add kernel config to
> enable/disable these messages during compilation.
[]
> -#define oz_trace(...) printk(TRACE_PREFIX __VA_ARGS__)
> +#define oz_trace(fmt, ...) dev_dbg(g_oz_wpan_dev,
convert all debug messages from printk to dev_dbg() & add kernel config to
enable/disable these messages during compilation.
Signed-off-by: Rupesh Gujare
---
drivers/staging/ozwpan/Kbuild|2 +-
drivers/staging/ozwpan/Kconfig |9 +
drivers/staging/ozwpan/ozcdev.c |9 +++
10 matches
Mail list logo