From: Jarkko Lavinen <jarkko.lavinen@nokia.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <david.woodhouse@intel.com>
Subject: Re: Cannot rmmod after call to add_mtd_blktrans_dev
Date: Tue, 28 Sep 2010 11:24:46 +0300 [thread overview]
Message-ID: <20100928082446.GA999@angel.research.nokia.com> (raw)
In-Reply-To: <1284851862.28101.2.camel@maxim-laptop>
On Sun, Sep 19, 2010 at 01:17:42AM +0200, ext Maxim Levitsky wrote:
> Please test the patch I have just posted on linux-mtd.
I tried the 1/3 patch sent on Sep 18 23:12 on top of 2.6.36-rc5.
Had some email problem and to pick the patch from web
archives. It didn't apply cleanly, but the merge conflict seemed
minor.
The patch seems to work. I am able to remove module but now
del_mtd_blktrans_dev(dev) relases my own device structure a bit
too early and have to protect it with extra kref_get() and
release it with blktrans_dev_put(dev).
Jarkko Lavinen
prev parent reply other threads:[~2010-09-28 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 12:20 Cannot rmmod after call to add_mtd_blktrans_dev Jarkko Lavinen
2010-09-08 14:43 ` Maxim Levitsky
2010-09-18 23:17 ` Maxim Levitsky
2010-09-28 8:24 ` Jarkko Lavinen [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=20100928082446.GA999@angel.research.nokia.com \
--to=jarkko.lavinen@nokia.com \
--cc=david.woodhouse@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@gmail.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