Subject: Re: [tip:sched/urgent] sched: Restore printk sanity
From: Joe Perches <joe@perches.com>
To: tytso@mit.edu
Cc: Ingo Molnar <mingo@elte.hu>, mingo@redhat.com, hpa@zytor.com,
       linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
       peterz@infradead.org, efault@gmx.de, akpm@linux-foundation.org,
       tglx@linutronix.de, linux-tip-commits@vger.kernel.org
In-Reply-To: <20091220221232.GC4887@thunk.org>
References: <1261315437.4314.6.camel@laptop>
	 <tip-3df0fc5b2e9d8092dcaeb5ae0b6753d85c851d66@git.kernel.org>
	 <1261335300.30458.209.camel@Joe-Laptop.home>
	 <20091220191531.GA17878@elte.hu>  <20091220221232.GC4887@thunk.org>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 20 Dec 2009 17:11:21 -0800
Message-ID: <1261357881.30458.235.camel@Joe-Laptop.home>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 611
Lines: 15

On Sun, 2009-12-20 at 17:12 -0500, tytso@mit.edu wrote:
> Maybe all
> printk's should be exempted from this, or at least if it's the format
> string which is breaking whatever the magic boundary happens to be?

If ever Andy Whitcroft gets 'round to releasing the
latest checkpatch from testing, the formats of
logging functions are exempted from long line checks.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/