From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mandeep Singh Baines Subject: [PATCH v1 0/6] Set printk priority level Date: Wed, 26 Jan 2011 15:29:24 -0800 Message-ID: <1296084570-31453-1-git-send-email-msb@chromium.org> References: <20110125235700.GR8008@google.com> Cc: linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org To: gregkh@suse.de, rjw@sisk.pl, mingo@redhat.com, akpm@linux-foundation.org Return-path: In-Reply-To: <20110125235700.GR8008@google.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org We've been burned by regressions/bugs which we later realized could have been triaged quicker if only we'd paid closer attention to dmesg. This patch series fixes printk()s which appear in the logs of the device I'm currently working on. I'd love to fix all such printks but there are hundreds of files and thousands of LOC affected: $ find . -name \*.c | xargs fgrep -c "printk(\"" | wc -l 16237 $ find . -name \*.c | xargs fgrep "printk(\"" | wc -l 20745 [PATCH 1/6] mm/page_alloc: use appropriate printk priority level [PATCH 2/6] arch/x86: use appropriate printk priority level [PATCH 3/6] PM: use appropriate printk priority level [PATCH 4/6] TTY: use appropriate printk priority level [PATCH 5/6] fs: use appropriate printk priority level [PATCH 6/6] taskstats: use appropriate printk priority level