All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kernel-janitor-discuss@lists.sourceforge.net,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current unclaimed 2.5 bugs on bugme.osdl.org
Date: Mon, 30 Dec 2002 09:02:58 -0800	[thread overview]
Message-ID: <299610000.1041267777@titus> (raw)
In-Reply-To: <1041255152.544.14.camel@zion.wanadoo.fr>

>> ID Sev Owner State Result Summary
>> 44 blo khoa@us.ibm.com OPEN radeonfb does not compile at all - seems
>> incomplete? or w...
>
> Beeing worked on by James Simmons and myself. Working version in the PPC
> tree, will be part of next round of fbdev updates
>
>> 69 nor mbligh@aracnet.com OPEN Framebuffer bug
>> 72 nor khoa@us.ibm.com OPEN Framebuffer scrolls at the wrong times/places
>> 79 nor khoa@us.ibm.com OPEN Framebuffer scrolling problem
>
> I've seen at least some of these discussed on the linux-fbdev mailing
> list, though I can't talk for the maintainer, I beleive they are beeing
> worked on.

OK, trouble is I need someone with a bugzilla account to assign these to.
I emailed James, if he doesn't want it, would you be willing to maintain
that subsection in bugzilla?

>> 117 nor mbligh@aracnet.com OPEN build failure: arch/ppc/kernel/process.c
>
> Works in current ppc bk tree, probably waiting for next round of merges
> by Paul Mackerras to Linus.

According to DaveJ, this should be fixed in 51 ... anyone able to test?

M.


  reply	other threads:[~2002-12-30 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  2:14 Current unclaimed 2.5 bugs on bugme.osdl.org Martin J. Bligh
2002-12-30  6:46 ` William Lee Irwin III
2002-12-30  9:05 ` Sam Ravnborg
2002-12-30 13:27 ` Alan Cox
2002-12-30 13:32 ` Benjamin Herrenschmidt
2002-12-30 17:02   ` Martin J. Bligh [this message]
2002-12-30 17:12     ` Dave Jones
2002-12-30 18:16     ` Benjamin Herrenschmidt
2002-12-30 21:15     ` Dr. David Alan Gilbert

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=299610000.1041267777@titus \
    --to=mbligh@aracnet.com \
    --cc=benh@kernel.crashing.org \
    --cc=kernel-janitor-discuss@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.