From: Jeff Garzik <jeff@garzik.org>
To: Saeed Bishara <saeed@marvell.com>
Cc: mlord@pobox.com, htejun@gmail.com, linux-ide@vger.kernel.org,
saeed.bishara@gmail.com, byron.bbradley@gmail.com,
tbm@cyrius.com
Subject: Re: [PATCH] sata_mv: remove iounmap in mv_platform_remove and use devm_iomap
Date: Wed, 20 Feb 2008 12:21:01 -0500 [thread overview]
Message-ID: <47BC617D.3030303@garzik.org> (raw)
In-Reply-To: <12033601481951-git-send-email-saeed@marvell.com>
Saeed Bishara wrote:
> this will fix crash bug when doing rmmod to the driver, this is because the
> port_stop function get called later and it could access the device's registers.
>
> Signed-off-by: Saeed Bishara <saeed@marvell.com>
> ---
> drivers/ata/sata_mv.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
applied
prev parent reply other threads:[~2008-02-20 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 18:42 [PATCH] sata_mv: remove iounmap in mv_platform_remove and use devm_iomap Saeed Bishara
2008-02-18 18:57 ` Mark Lord
2008-02-19 23:25 ` Tejun Heo
2008-02-20 17:21 ` 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=47BC617D.3030303@garzik.org \
--to=jeff@garzik.org \
--cc=byron.bbradley@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
--cc=saeed.bishara@gmail.com \
--cc=saeed@marvell.com \
--cc=tbm@cyrius.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).