From: Marco Stornelli <marco.stornelli@gmail.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-embedded@vger.kernel.org, akpm@linux-foundation.org,
dwm2@infradead.org, linux-kernel@vger.kernel.org,
mpm@selenic.com, paul.gortmaker@windriver.com
Subject: Re: [PATCH, RFC] panic-note: Annotation from user space for panics
Date: Thu, 12 Nov 2009 19:00:17 +0100 [thread overview]
Message-ID: <4AFC4D31.2000101@gmail.com> (raw)
In-Reply-To: <20091112021322.GA6166@dvomlehn-lnx2.corp.sa.net>
Sincerely, I don't understand why we should involve the kernel to gather
this kind of information when we can use other (user-space) tools, only
to have "all" in a single report maybe? I think it's a bit weak reason
to include this additional behavior in the kernel.
David VomLehn ha scritto:
> Allows annotation of panics to include platform information. It's no big
> deal to collect information, but way helpful when you are collecting
> failure reports from a eventual base of millions of systems deployed in
> other people's homes.
>
Marco
next prev parent reply other threads:[~2009-11-12 18:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 2:13 [PATCH, RFC] panic-note: Annotation from user space for panics David VomLehn
2009-11-12 18:00 ` Marco Stornelli [this message]
2009-11-12 21:56 ` David VomLehn
2009-11-13 8:10 ` Simon Kagstrom
2009-11-13 11:45 ` Artem Bityutskiy
2009-11-13 11:59 ` Simon Kagstrom
2009-11-13 14:16 ` Artem Bityutskiy
2009-11-14 8:28 ` Marco Stornelli
2009-11-17 8:53 ` Artem Bityutskiy
2009-11-17 12:45 ` Marco Stornelli
2009-11-17 13:10 ` Artem Bityutskiy
2009-11-17 15:45 ` Eric W. Biederman
2009-11-17 23:56 ` David VomLehn
2009-11-18 0:28 ` Eric W. Biederman
2009-11-18 0:53 ` David VomLehn
2009-11-18 9:01 ` Américo Wang
2009-11-18 17:01 ` Eric W. Biederman
2009-11-18 0:56 ` Matt Mackall
2009-11-18 16:07 ` Eric W. Biederman
2009-11-18 17:52 ` Tim Bird
2009-11-18 18:16 ` Eric W. Biederman
2009-11-18 18:16 ` Eric W. Biederman
2009-11-18 8:26 ` Artem Bityutskiy
2009-11-17 17:53 ` Marco Stornelli
2009-11-12 18:06 ` Matt Mackall
2009-11-12 21:58 ` David VomLehn
2009-11-13 11:35 ` Artem Bityutskiy
2009-11-12 19:50 ` Paul Gortmaker
2009-11-12 22:09 ` David VomLehn
2009-11-13 11:50 ` Shargorodsky Atal (EXT-Teleca/Helsinki)
2009-11-13 11:26 ` Artem Bityutskiy
2009-11-17 9:03 ` Artem Bityutskiy
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=4AFC4D31.2000101@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvomlehn@cisco.com \
--cc=dwm2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul.gortmaker@windriver.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 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.