All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dave Jones <davej@suse.de>
Cc: Erik Andersen <andersen@codepoet.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb fix, fixed
Date: Mon, 14 Jan 2002 18:55:51 -0500	[thread overview]
Message-ID: <3C437007.595C5ADE@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201150036150.22605-100000@Appserv.suse.de>

Dave Jones wrote:
> 
> On Sun, 13 Jan 2002, Erik Andersen wrote:
> 
> > > This patch is needed to make radeonfb compile and work.
> > > It is based on an earlier patch on the list attributed to
> > > Ani Joshi, plus adds the needed devinit fix.
> > Oops.  That patch had some crap in it.  Lets try that again.
> 
> Uncompressed, that patch was just 4kb. When not too big, it's
> considered acceptable (and preferred) to send them as plaintext
> to the list for ease of quoting.
> 
> Patch looks ok, but this bit..
> 
> diff -urN linux/drivers/video.virgin/radeonfb.c
> linux/drivers/video/radeonfb.c
> --- linux/drivers/video.virgin/radeonfb.c   Sun Jan 13 19:09:54 2002
> +++ linux/drivers/video/radeonfb.c  Sun Jan 13 19:41:00 2002
> @@ -686,7 +686,7 @@
>     name:       "radeonfb",
>     id_table:   radeonfb_pci_table,
>     probe:      radeonfb_pci_register,
> -   remove:     radeonfb_pci_unregister,
> +   remove:     __devexit_p(radeonfb_pci_unregister),
>  };
> 
> Is that really needed ?  Hotplugable radeons ?

To rant on a general topic, this wholesale converting drivers to
__devexit without much thought, to fix a simple compile error, may wind
up biting users in the ass later on.  Sometimes, like in the case of
radeonfb and many other fbdev drivers, the driver is -not- able to deal
with all hotplug issues without further fixes.  Fixing radeonfb as with
the above simply hides those problems...

	Jeff


-- 
Jeff Garzik      | Alternate titles for LOTR:
Building 1024    | Fast Times at Uruk-Hai
MandrakeSoft     | The Took, the Elf, His Daughter and Her Lover
                 | Samwise Gamgee: International Hobbit of Mystery

      reply	other threads:[~2002-01-14 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 20:30 Linux 2.4.18pre3 Marcelo Tosatti
2002-01-10 23:09 ` Eyal Lebedinsky
2002-01-10 23:44 ` Adrian Bunk
2002-01-11  5:50   ` Keith Owens
2002-01-11 23:44 ` Linux 2.4.18pre3 - miata pci dma fix Kurt Garloff
2002-01-11 23:54   ` Richard Henderson
2002-01-14  2:59 ` radeonfb fix Erik Andersen
2002-01-14  3:14   ` radeonfb fix, fixed Erik Andersen
2002-01-14 23:38     ` Dave Jones
2002-01-14 23:55       ` Jeff Garzik [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=3C437007.595C5ADE@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andersen@codepoet.org \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.