Re: [tip:sched/urgent] sched: Restore printk sanity
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:sched/urgent] sched: Restore printk sanity
- From: Joe Perches <joe@xxxxxxxxxxx>
- Date: Sun, 20 Dec 2009 17:11:21 -0800
- Cc: Ingo Molnar <mingo@xxxxxxx>, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, peterz@xxxxxxxxxxxxx, efault@xxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20091220221232.GC4887@xxxxxxxxx>
- References: <1261315437.4314.6.camel@laptop> <tip-3df0fc5b2e9d8092dcaeb5ae0b6753d85c851d66@xxxxxxxxxxxxxx> <1261335300.30458.209.camel@xxxxxxxxxxxxxxx> <20091220191531.GA17878@xxxxxxx> <20091220221232.GC4887@xxxxxxxxx>
On Sun, 2009-12-20 at 17:12 -0500, tytso@xxxxxxx 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-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
