From: "Adrian McMenamin" <lkmladrian@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>,
Adrian McMenamin <lkmladrian@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-sh@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH 2/3] Add GD-Rom support to the SEGA Dreamcast
Date: Thu, 20 Dec 2007 21:53:54 +0000 [thread overview]
Message-ID: <8b67d60712201353y71a85498p9d77f1f21761856c@mail.gmail.com> (raw)
In-Reply-To: <20071216095019.GA12184@linux-sh.org>
On 16/12/2007, Paul Mundt <lethal@linux-sh.org> wrote:
>
> Also, __devinit/__devexit annotations?
>
Is there any difference between __init and __devint? I am using
__init/__exit already
> > +static struct platform_driver gdrom_driver = {
> > + .probe = probe_gdrom,
> > + .remove = remove_gdrom,
>
> __devexit_p()?
>
> > +static void __exit exit_gdrom(void)
> > +{
> > + blk_cleanup_queue(gd.gdrom_rq);
> > + free_irq(HW_EVENT_GDROM_CMD, &gd);
> > + free_irq(HW_EVENT_GDROM_DMA, &gd);
> > + del_gendisk(gd.disk);
> > + if (gdrom_major)
> > + unregister_blkdev(gdrom_major, GDROM_DEV_NAME);
> > + platform_device_unregister(pd);
> > + platform_driver_unregister(&gdrom_driver);
> > + if (gd.toc)
> > + kfree(gd.toc);
> > +}
> > +
> Ah, here's where you do the rest of the cleanup. This is non-intuitive,
> remove should balance the work done by probe and exit the work done by
> init.
>
next prev parent reply other threads:[~2007-12-20 21:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 0:21 [PATCH 2/3] Add GD-Rom support to the SEGA Dreamcast Adrian McMenamin
2007-12-16 9:50 ` Paul Mundt
2007-12-16 10:09 ` Christoph Hellwig
2007-12-16 17:32 ` Adrian McMenamin
2007-12-16 21:59 ` Paul Mundt
2007-12-17 0:06 ` Adrian McMenamin
2007-12-16 18:05 ` Adrian McMenamin
2007-12-17 23:20 ` Jan Engelhardt
2007-12-20 21:53 ` Adrian McMenamin [this message]
2007-12-21 5:24 ` Paul Mundt
2007-12-16 21:01 ` Mike Frysinger
2007-12-17 14:06 ` Jens Axboe
2007-12-17 14:36 ` Adrian McMenamin
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=8b67d60712201353y71a85498p9d77f1f21761856c@mail.gmail.com \
--to=lkmladrian@gmail.com \
--cc=axboe@kernel.dk \
--cc=lethal@linux-sh.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 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).