From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ahmed S. Darwish" <darwish.07@gmail.com>
Cc: "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Zhou" <David1.Zhou@amd.com>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Matt Fleming" <matt@codeblueprint.co.uk>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"John Ogness" <john.ogness@linutronix.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: DRM-based Oops viewer
Date: Tue, 12 Mar 2019 12:20:01 +0200 [thread overview]
Message-ID: <87wol4jsxa.fsf@intel.com> (raw)
In-Reply-To: <20190311221223.GA3344@darwi-home-pc>
On Mon, 11 Mar 2019, "Ahmed S. Darwish" <darwish.07@gmail.com> wrote:
> Hello Jani,
>
> On Mon, Mar 11, 2019 at 11:04:19AM +0200, Jani Nikula wrote:
>> On Sun, 10 Mar 2019, "Ahmed S. Darwish" <darwish.07@gmail.com> wrote:
>> Please first better define what you want to achieve.
>>
>
> Oh I thought this was clear..
>
> What I want to achieve is:
>
> - for normal day-to-day x86 laptops users
> - properly inform the user when a kernel panic happens during
> a running graphical session (e.g. wayland/gnome/kde/...).
Thanks for the detailed reply. It always helps to start with the problem
you want to solve or end goal you want to reach.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-03-12 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 1:31 DRM-based Oops viewer Ahmed S. Darwish
2019-03-10 8:44 ` Martin Steigerwald
2019-03-11 9:04 ` Jani Nikula
2019-03-11 13:49 ` Daniel Vetter
2019-03-11 23:39 ` Ahmed S. Darwish
2019-03-11 22:12 ` Ahmed S. Darwish
2019-03-12 10:20 ` Jani Nikula [this message]
2019-03-11 12:10 ` Joonas Lahtinen
2019-03-11 17:47 ` Noralf Trønnes
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=87wol4jsxa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=David1.Zhou@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=ard.biesheuvel@linaro.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=darwish.07@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=rodrigo.vivi@intel.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).