From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 23 Jun 2010 17:23:59 +0200 From: Andrew Lunn Message-ID: <20100623152359.GL15420@lunn.ch> References: <201006231620.11058.lindner_marek@yahoo.de> <1277302839-20197-1-git-send-email-lindner_marek@yahoo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1277302839-20197-1-git-send-email-lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: add routing debug log accessible via debugfs Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking Cc: Marek Lindner , b.a.t.m.a.n@lists.open-mesh.net On Wed, Jun 23, 2010 at 04:20:38PM +0200, Marek Lindner wrote: Hi Marek > - if (bat_debug_type(type)) \ > - printk(KERN_DEBUG "batman-adv:" fmt, ## arg); \ did you think about keeping this? Maybe use some of the spare bits of debug to indicate what goes into the circular buffer and what goes to the kernel log? I don't see the two schemes are mutually exclusive. "Normal" kernel hackers will look in the normal kernel logging places and could be a bit surprised when its not there. Andrew