From: Dan Carpenter <dan.carpenter@oracle.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-omap@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>,
Felipe Contreras <felipe.contreras@nokia.com>
Subject: Re: [PATCH] staging: tidspbridge: enable watchdog by default
Date: Fri, 10 Feb 2012 21:00:15 +0300 [thread overview]
Message-ID: <20120210180015.GF4141@mwanda> (raw)
In-Reply-To: <CAMP44s3r1-rt6HqgmVuB_Kjd1LSo-75m=6GERUt+ATewBaFw-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Fri, Feb 10, 2012 at 01:30:48AM +0200, Felipe Contreras wrote:
> It's not an oops, it's a warning, and again, it depends on the
> firmware being used. We don't have control over that, and we have no
> way to detect if this feature is there. It's up to the user.
Perhaps just remove the warning message and handle the condition
instead of printing a stack dump? The user should be triggering
stack dumps. What on earth?
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-10 17:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:01 [PATCH] staging: tidspbridge: enable watchdog by default Felipe Contreras
2012-02-01 1:12 ` Greg KH
2012-02-01 1:37 ` Felipe Contreras
2012-02-01 3:22 ` Justin P. Mattock
2012-02-01 8:11 ` Felipe Contreras
2012-02-01 20:22 ` Ramirez Luna, Omar
2012-02-01 3:44 ` Greg KH
2012-02-01 7:26 ` Felipe Contreras
2012-02-09 17:35 ` Greg KH
2012-02-09 18:41 ` Felipe Contreras
2012-02-09 18:43 ` Felipe Contreras
2012-02-09 18:59 ` Greg KH
2012-02-09 23:30 ` Felipe Contreras
2012-02-10 0:45 ` Ramirez Luna, Omar
2012-02-10 5:18 ` Greg KH
2012-02-10 15:35 ` Justin P. Mattock
2012-02-10 16:05 ` Felipe Contreras
2012-02-10 16:14 ` Justin P. Mattock
2012-02-10 16:16 ` Greg KH
2012-02-10 16:29 ` Felipe Contreras
2012-02-10 16:16 ` Felipe Contreras
2012-02-10 17:48 ` Greg KH
2012-02-14 1:12 ` Ramirez Luna, Omar
2012-02-10 18:00 ` Dan Carpenter [this message]
2012-02-10 19:42 ` Felipe Contreras
2012-02-10 20:35 ` Dan Carpenter
2012-02-10 20:43 ` Felipe Contreras
[not found] ` <CAB-zwWhSoiMNVGQ=u=6-Umte-AaP9Qih8QMJFTyk8pjXaXysLg@mail.gmail.com>
2012-02-11 23:03 ` Felipe Contreras
2012-02-14 1:06 ` Ramirez Luna, Omar
2012-02-14 16:23 ` Felipe Contreras
2012-02-15 2:56 ` Ramirez Luna, Omar
2012-02-15 9:43 ` Víctor M. Jáquez L.
2012-02-15 11:41 ` Felipe Contreras
2012-02-15 12:02 ` Víctor M. Jáquez L.
2012-02-15 22:32 ` Omar Ramirez Luna
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=20120210180015.GF4141@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=justinmattock@gmail.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.