From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757426AbYGHRAr (ORCPT ); Tue, 8 Jul 2008 13:00:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757555AbYGHQ5z (ORCPT ); Tue, 8 Jul 2008 12:57:55 -0400 Received: from casper.infradead.org ([85.118.1.10]:55147 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756932AbYGHQ5y (ORCPT ); Tue, 8 Jul 2008 12:57:54 -0400 Date: Tue, 8 Jul 2008 09:38:03 -0700 From: Arjan van de Ven To: linux-kernel@vger.kernel.org Cc: akpm@linux-foundation.org, mingo@elte.hu Subject: [patch 0/17] Series to introduce WARN()... a WARN_ON() variant that takes printk arguments Message-ID: <20080708093803.59a53c27@infradead.org> Organization: Intel X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This patch series introduces WARN(), which is a WARN_ON() variant that takes printk() like arguments. This was done after both akpm and I hit several cases where this would have been useful; in addition, with WARN(), we put the printk string inside the -----[ cut here ]----- section, making it more likely that users (and tools like kerneloops) pick up the message in addition to just the bare WARNING. The first few patches have been in -mm for a long time; the later ones are newer and introduce more users of WARN().