[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfuBxyToA9-=c3H88GGba3GFX64kdbP4OCEC0f4trnBnjpU-w@mail.gmail.com>
Date: Thu, 30 Aug 2012 21:48:12 -0600
From: Jim Cromie <jim.cromie@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"David S. Miller" <davem@...emloft.net>,
Jason Baron <jbaron@...hat.com>, Kay Sievers <kay@...y.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] dev_<level> and dynamic_debug cleanups
On Thu, Aug 30, 2012 at 11:43 AM, Jim Cromie <jim.cromie@...il.com> wrote:
> On Sun, Aug 26, 2012 at 5:25 AM, Joe Perches <joe@...ches.com> wrote:
>> The recent commit to fix dynamic_debug was a bit unclean.
>> Neaten the style for dynamic_debug.
>> Reduce the stack use of message logging that uses netdev_printk
>> Add utility functions dev_printk_emit and dev_vprintk_emit for /dev/kmsg.
>>
>> Joe Perches (5):
>> dev_dbg/dynamic_debug: Update to use printk_emit, optimize stack
>> netdev_printk/dynamic_netdev_dbg: Directly call printk_emit
>> netdev_printk/netif_printk: Remove a superfluous logging colon
>> dev: Add dev_vprintk_emit and dev_printk_emit
>> device and dynamic_debug: Use dev_vprintk_emit and dev_printk_emit
>>
>
> Ive tested this on 2 builds differing only by DYNAMIC_DEBUG
> It works for me on x86-64
>
> However, I just booted a non-dyndbg build on x86-32, and got this.
>
Ok, transient error, went away with a clean build.
tested-by: Jim Cromie <jim.cromie@...il.com>
thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists