From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p43KNms2028128 for ; Tue, 3 May 2011 15:23:49 -0500 Received: from mail.perches.com (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 493B31E1AF31 for ; Tue, 3 May 2011 13:27:25 -0700 (PDT) Received: from mail.perches.com (mail.perches.com [173.55.12.10]) by cuda.sgi.com with ESMTP id g6RdT78rctw8uwhS for ; Tue, 03 May 2011 13:27:25 -0700 (PDT) Subject: Re: [PATCH] xfs: kill off xfs_printk() From: Joe Perches In-Reply-To: References: Date: Tue, 03 May 2011 13:27:24 -0700 Message-ID: <1304454444.1788.34.camel@Joe-Laptop> Mime-Version: 1.0 List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Alex Elder Cc: xfs@oss.sgi.com On Tue, 2011-05-03 at 15:14 -0500, Alex Elder wrote: > From: Joe Perches > > xfs_alert_tag() can be defined using xfs_alert(), and thereby avoid > using xfs_printk() altogether. This is the only remaining use of > xfs_printk(), so changing it this way means xfs_printk() can simply > be eliminated.can simply be eliminated.can simply be eliminated.can > simply be eliminated.can simply be eliminated.can simply be > eliminated.can simply be eliminated.can simply be eliminated.can > simply be eliminated. Recursion overflow? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs