public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.2-pre3: parport_pc init_module bug
Date: Wed, 14 Feb 2001 11:18:06 +0000	[thread overview]
Message-ID: <20010214111806.Y9459@redhat.com> (raw)
In-Reply-To: <20010214105332.U9459@redhat.com> <Pine.LNX.3.96.1010214051314.12910E-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: <Pine.LNX.3.96.1010214051314.12910E-100000@mandrakesoft.mandrakesoft.com>; from jgarzik@mandrakesoft.mandrakesoft.com on Wed, Feb 14, 2001 at 05:14:19AM -0600

On Wed, Feb 14, 2001 at 05:14:19AM -0600, Jeff Garzik wrote:

> Should the call to pci_unregister_driver in cleanup_module be
> conditional on registered_parport as well?  I didn't check...

No. (cleanup_module is only called if init_module succeeded.)

> Also, is it possible to convert parport_pc to new-style module_init()?

Certainly, in 2.5, or when it's needed to fix a bug.

Tim.
*/

  reply	other threads:[~2001-02-14 11:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13 23:43 [patch] 2.4.2-pre3: parport_pc init_module bug Tim Waugh
2001-02-14  8:03 ` Jeff Garzik
2001-02-14  8:53   ` James Sutherland
2001-02-14 10:53   ` Tim Waugh
2001-02-14 11:14     ` Jeff Garzik
2001-02-14 11:18       ` Tim Waugh [this message]
2001-02-14 11:21   ` Andrew Morton
2001-02-14 11:17     ` Tim Waugh
2001-02-14 11:24       ` Jeff Garzik
2001-02-14 11:40         ` Philipp Rumpf
2001-02-14 17:25           ` Grant Grundler
2001-02-14 21:12             ` Philipp Rumpf
2001-02-15  2:26               ` Grant Grundler
2001-02-18 15:05             ` Jeff Garzik
2001-02-14 11:31       ` Philipp Rumpf
2001-02-14 11:17     ` Jeff Garzik

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=20010214111806.Y9459@redhat.com \
    --to=twaugh@redhat.com \
    --cc=jgarzik@mandrakesoft.mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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