From: Coywolf Qi Hunt <qiyong@fc-cn.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] oops-tracing: mention digital photos
Date: Tue, 15 Nov 2005 16:58:02 +0800 [thread overview]
Message-ID: <20051115085802.GA3320@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0511141354570.8548@shark.he.net>
On Mon, Nov 14, 2005 at 01:56:03PM -0800, Randy.Dunlap wrote:
> On Mon, 14 Nov 2005, Dave Jones wrote:
>
> > On Sun, Nov 13, 2005 at 07:02:57PM -0800, Linux Kernel wrote:
> > > tree 849707fda27c41466eabae0119d6386826ddb7dc
> > > parent 113fab1386f0093602d9f48b424b945cafd3db23
> > > author Diego Calleja <diegocg@gmail.com> Mon, 14 Nov 2005 08:07:40 -0800
> > > committer Linus Torvalds <torvalds@g5.osdl.org> Mon, 14 Nov 2005 10:14:17 -0800
> > >
> > > [PATCH] oops-tracing: mention digital photos
> > >
> > > Signed-off-by: Andrew Morton <akpm@osdl.org>
> > > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> >
> > Something I've found handy countless times when users do this..
> >
> > Signed-off-by: Dave Jones <davej@redhat.com>
>
> I've mentioned that a few times also (to bug reporters),
> but your doc. is better than mine was.
I had come up to this idea before too, but never tried it. The higher
resolution mode is ugly and fb was buggy at that time (not sure now).
I wonder if it's feasible to implement panic messages showing cyclically,
or better like more (1).
Coywolf
prev parent reply other threads:[~2005-11-15 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511140302.jAE32voh027313@hera.kernel.org>
2005-11-14 21:52 ` [PATCH] oops-tracing: mention digital photos Dave Jones
2005-11-14 21:56 ` Randy.Dunlap
2005-11-15 8:58 ` Coywolf Qi Hunt [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=20051115085802.GA3320@localhost.localdomain \
--to=qiyong@fc-cn.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@osdl.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.