From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752917Ab2H3RoS (ORCPT ); Thu, 30 Aug 2012 13:44:18 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:54794 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750797Ab2H3RoQ (ORCPT ); Thu, 30 Aug 2012 13:44:16 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Jim Cromie Date: Thu, 30 Aug 2012 11:43:45 -0600 Message-ID: Subject: Re: [PATCH 0/5] dev_ and dynamic_debug cleanups To: Joe Perches Cc: Andrew Morton , netdev@vger.kernel.org, Greg Kroah-Hartman , "David S. Miller" , Jason Baron , Kay Sievers , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 26, 2012 at 5:25 AM, Joe Perches 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. root@voyage:~# dmesg | grep Unknown mac80211: Unknown symbol __dynamic_dev_dbg (err 0) mac80211: Unknown symbol __dynamic_pr_debug (err 0) scx200_acb: Unknown symbol __dynamic_dev_dbg (err 0) scx200_acb: Unknown symbol __dynamic_pr_debug (err 0) hwmon: Unknown symbol __dynamic_dev_dbg (err 0) nsc_gpio: Unknown symbol __dynamic_dev_dbg (err 0) nsc_gpio: Unknown symbol __dynamic_dev_dbg (err 0) root@voyage:~# It may be my error, will investigate asap, but wanted to report now. thanks