From: Joe Perches <joe@perches.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/3] Add Firmware Info, Warn, and Bug messages
Date: Mon, 02 Dec 2013 09:34:03 -0800 [thread overview]
Message-ID: <1386005643.2680.7.camel@joe-AO722> (raw)
In-Reply-To: <1385997579-22240-1-git-send-email-prarit@redhat.com>
On Mon, 2013-12-02 at 10:19 -0500, Prarit Bhargava wrote:
> Logging and tracking firmware bugs in the kernel has long been an issue
> for system administrators. The current kernel does not have a good
> uniform method of reporting firmware bugs and the code in the kernel is a
> mix of printk's and WARN_ONs. This causes problems for both system
> administrators and QA engineers who attempt to diagnose problems within
> the kernel.
It'd be simpler if you introduced the macros in one patch
and then added patches that used them separately.
prev parent reply other threads:[~2013-12-02 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 15:19 Prarit Bhargava
2013-12-02 15:19 ` [PATCH 1/3] Introduce FW_INFO* functions and messages Prarit Bhargava
2013-12-03 21:21 ` Andrew Morton
2013-12-04 11:51 ` Prarit Bhargava
2013-12-04 17:20 ` Joe Perches
2013-12-04 18:22 ` Arnd Bergmann
2013-12-05 11:30 ` Matt Fleming
2013-12-05 15:55 ` Joe Perches
2013-12-06 12:30 ` Matt Fleming
2013-12-16 13:01 ` Prarit Bhargava
2013-12-16 16:31 ` Joe Perches
2013-12-02 15:19 ` [PATCH 2/3] Introduce FW_WARN* " Prarit Bhargava
2013-12-02 15:19 ` [PATCH 3/3] Introduce FW_BUG* " Prarit Bhargava
2013-12-02 17:34 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1386005643.2680.7.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®