linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
	linux-nvidia@lists.surfsouth.com,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] Re: 2.6.11-rc5, rivafb i2c oops, bogus error handling
Date: Tue, 1 Mar 2005 21:58:40 +0100	[thread overview]
Message-ID: <20050301205840.GA20949@suse.de> (raw)
In-Reply-To: <200502282241.55815.adaplas@hotpop.com>

 On Mon, Feb 28, Antonino A. Daplas wrote:

> On Monday 28 February 2005 04:32, Olaf Hering wrote:
> >  On Wed, Feb 23, Linus Torvalds wrote:
> > > This time it's really supposed to be a quickie, so people who can, please
> > > check it out, and we'll make the real 2.6.11 asap.
> >
> > Here is another one, probably not new.
> > Is riva_get_EDID_i2c a bit too optimistic by not having a $i2cadapter_ok
> > member in riva_par->riva_i2c_chan? It calls riva_probe_i2c_connector
> > even if riva_create_i2c_busses fails to register all 3 busses.

Side note:

<linux-nvidia@lists.surfsouth.com>: connect to
    lists.surfsouth.com[216.128.200.12]: Connection timed out

Is this one supposed to work? perhaps the MAINTAINERS entry needs an
update.

      parent reply	other threads:[~2005-03-01 20:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0502232014190.18997@ppc970.osdl.org>
     [not found] ` <20050224145049.GA21313@suse.de>
     [not found]   ` <1109287708.15026.25.camel@gaston>
     [not found]     ` <20050225070813.GA13735@suse.de>
     [not found]       ` <1109316551.14993.63.camel@gaston>
2005-02-25 17:29         ` 2.6.11-rc5 Olaf Hering
2005-02-25 17:59           ` [Linux-fbdev-devel] 2.6.11-rc5 James Simmons
2005-02-25 20:24             ` Olaf Hering
2005-02-25 21:21               ` [Linux-fbdev-devel] " Olaf Hering
2005-02-25 23:30                 ` Olaf Hering
2005-02-26  1:01                   ` Benjamin Herrenschmidt
2005-02-26  9:52                     ` Giuseppe Bilotta
2005-02-26  0:58                 ` Benjamin Herrenschmidt
2005-02-26  0:57               ` Benjamin Herrenschmidt
2005-02-26  0:54           ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-26  0:41   ` 2.6.11-rc5 Olaf Hering
2005-02-26  0:49     ` 2.6.11-rc5 Linus Torvalds
2005-02-26  0:53       ` 2.6.11-rc5 Olaf Hering
2005-02-26  1:04         ` 2.6.11-rc5 Linus Torvalds
2005-02-26  1:08       ` 2.6.11-rc5 Buttchereit, Axel (XL)
2005-02-26  1:17         ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-02-26  1:13     ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-26  7:41       ` [Linux-fbdev-devel] 2.6.11-rc5 Antonino A. Daplas
2005-02-27  8:07       ` 2.6.11-rc5 Geert Uytterhoeven
2005-02-27 20:32 ` 2.6.11-rc5, rivafb i2c oops, bogus error handling Olaf Hering
2005-02-28 14:41   ` Antonino A. Daplas
2005-03-01 12:02     ` [Linux-fbdev-devel] " Olaf Hering
2005-03-01 20:58     ` Olaf Hering [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=20050301205840.GA20949@suse.de \
    --to=olh@suse.de \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvidia@lists.surfsouth.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 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).