From: "alois.klingler@chello.at" <alois.klingler@chello.at>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: MadLoisae@gmx.net, linux-fbdev-devel@lists.sourceforge.net,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel oops with framebuffer device vt8623fb
Date: Tue, 05 Aug 2008 13:17:39 +0200 [thread overview]
Message-ID: <489836D3.2050008@chello.at> (raw)
In-Reply-To: <20080728204817.ebaa621b.akpm@linux-foundation.org>
Hi!
This issue is still not fixed in 2.6.26.1 - may be there a way to commit
it in 2.6.26.2?
Still, the provided patch I got on 07/17/2008 works great ...
Thanks, anyway!
kind regards, Alois
Andrew Morton wrote:
> On Thu, 17 Jul 2008 03:39:18 +0200 Ondrej Zajicek <santiago@crfreenet.org> wrote:
>
>
>> On Wed, Jul 16, 2008 at 07:00:02PM +0200, MadLoisae@gmx.net wrote:
>>
>>> Hi!
>>>
>>> I've updated my machine from 2.6.25.11 to 2.6.26 and I think I've found
>>> a problem.
>>>
>>> If I load the module vt8623fb i get a kernel oops, if the VIA 8623
>>> display framebuffer driver is compiled direct into kernel the system
>>> hangs up very early at booting the kernel.
>>>
>> I am sorry for mistake, here is a patch for 2.6.26 fixing the bug:
>>
>> Signed-off-by: Ondrej Zajicek <santiago@crfreenet.org>
>>
>
> I went back through the email thread and wrote your changelog for you.
> Not a very good one though.
>
> It would be better were you to write your changelogs, please.
>
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
WARNING: multiple messages have this Message-ID (diff)
From: "alois.klingler@chello.at" <alois.klingler@chello.at>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ondrej Zajicek <santiago@crfreenet.org>,
MadLoisae@gmx.net, Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: kernel oops with framebuffer device vt8623fb
Date: Tue, 05 Aug 2008 13:17:39 +0200 [thread overview]
Message-ID: <489836D3.2050008@chello.at> (raw)
In-Reply-To: <20080728204817.ebaa621b.akpm@linux-foundation.org>
Hi!
This issue is still not fixed in 2.6.26.1 - may be there a way to commit
it in 2.6.26.2?
Still, the provided patch I got on 07/17/2008 works great ...
Thanks, anyway!
kind regards, Alois
Andrew Morton wrote:
> On Thu, 17 Jul 2008 03:39:18 +0200 Ondrej Zajicek <santiago@crfreenet.org> wrote:
>
>
>> On Wed, Jul 16, 2008 at 07:00:02PM +0200, MadLoisae@gmx.net wrote:
>>
>>> Hi!
>>>
>>> I've updated my machine from 2.6.25.11 to 2.6.26 and I think I've found
>>> a problem.
>>>
>>> If I load the module vt8623fb i get a kernel oops, if the VIA 8623
>>> display framebuffer driver is compiled direct into kernel the system
>>> hangs up very early at booting the kernel.
>>>
>> I am sorry for mistake, here is a patch for 2.6.26 fixing the bug:
>>
>> Signed-off-by: Ondrej Zajicek <santiago@crfreenet.org>
>>
>
> I went back through the email thread and wrote your changelog for you.
> Not a very good one though.
>
> It would be better were you to write your changelogs, please.
>
>
>
next prev parent reply other threads:[~2008-08-05 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 17:00 kernel oops with framebuffer device vt8623fb MadLoisae
2008-07-16 17:13 ` Alexey Dobriyan
2008-07-16 19:30 ` MadLoisae
2008-07-17 1:39 ` Ondrej Zajicek
2008-07-17 1:39 ` Ondrej Zajicek
2008-07-17 11:21 ` alois.klingler
2008-07-17 11:23 ` MadLoisae
2008-07-29 3:48 ` Andrew Morton
2008-07-29 3:48 ` Andrew Morton
2008-08-05 11:17 ` alois.klingler [this message]
2008-08-05 11:17 ` alois.klingler
2008-08-05 16:12 ` Andrew Morton
2008-08-05 16:12 ` Andrew Morton
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=489836D3.2050008@chello.at \
--to=alois.klingler@chello.at \
--cc=MadLoisae@gmx.net \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@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.