From: Stephane Chazelas <stephane.chazelas@emerson.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2.6.24] block2mtd: removing a device and typo fixes
Date: Wed, 20 Feb 2008 16:55:13 +0000 [thread overview]
Message-ID: <chaz20080220165513.GU4539@artesyncp.com> (raw)
In-Reply-To: <20080220164226.GF5539@lazybastard.org>
2008-02-20 17:42:27 +0100, Jörn Engel:
> On Wed, 20 February 2008 14:36:46 +0000, Stephane Chazelas wrote:
> >
> > At the moment, when we bind a mtd device to a block device, we
> > don't increase the refcount. When a mtdblock on a block2mtd, the
> > refcount is not increased either (the mtdblock's one is I
> > guess).
>
> That is a bug then.
[...]
Well, given that there is no API to unbind a mtd to a block
device, otherwise, we would never be able to unload block2mtd.
So fare, unloading block2mtd was the only way to unbind a mtd
from a block device.
Cheers,
Stephane
WARNING: multiple messages have this Message-ID (diff)
From: Stephane Chazelas <stephane.chazelas@emerson.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2.6.24] block2mtd: removing a device and typo fixes
Date: Wed, 20 Feb 2008 16:55:13 +0000 [thread overview]
Message-ID: <chaz20080220165513.GU4539@artesyncp.com> (raw)
In-Reply-To: <20080220164226.GF5539@lazybastard.org>
2008-02-20 17:42:27 +0100, Jörn Engel:
> On Wed, 20 February 2008 14:36:46 +0000, Stephane Chazelas wrote:
> >
> > At the moment, when we bind a mtd device to a block device, we
> > don't increase the refcount. When a mtdblock on a block2mtd, the
> > refcount is not increased either (the mtdblock's one is I
> > guess).
>
> That is a bug then.
[...]
Well, given that there is no API to unbind a mtd to a block
device, otherwise, we would never be able to unload block2mtd.
So fare, unloading block2mtd was the only way to unbind a mtd
from a block device.
Cheers,
Stephane
next prev parent reply other threads:[~2008-02-20 16:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 13:47 [PATCH 2.6.24] block2mtd: removing a device and typo fixes Stephane Chazelas
2008-02-12 13:47 ` Stephane Chazelas
2008-02-12 15:21 ` Jörn Engel
2008-02-12 15:21 ` Jörn Engel
2008-02-12 16:10 ` Stephane Chazelas
2008-02-12 16:10 ` Stephane Chazelas
2008-02-19 15:08 ` Jörn Engel
2008-02-19 15:08 ` Jörn Engel
2008-02-19 22:33 ` Arnd Bergmann
2008-02-19 22:33 ` Arnd Bergmann
2008-02-20 6:43 ` Jörn Engel
2008-02-20 6:43 ` Jörn Engel
2008-02-20 14:43 ` Stephane Chazelas
2008-02-20 14:43 ` Stephane Chazelas
2008-02-20 16:30 ` Jörn Engel
2008-02-20 16:30 ` Jörn Engel
2008-02-20 17:02 ` Stephane Chazelas
2008-02-20 17:02 ` Stephane Chazelas
2008-02-20 17:22 ` Jörn Engel
2008-02-20 17:22 ` Jörn Engel
2008-02-20 17:30 ` Stephane Chazelas
2008-02-20 17:30 ` Stephane Chazelas
2008-02-23 15:33 ` Jörn Engel
2008-02-23 15:33 ` Jörn Engel
2008-02-20 14:36 ` Stephane Chazelas
2008-02-20 14:36 ` Stephane Chazelas
2008-02-20 16:42 ` Jörn Engel
2008-02-20 16:42 ` Jörn Engel
2008-02-20 16:55 ` Stephane Chazelas [this message]
2008-02-20 16:55 ` Stephane Chazelas
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=chaz20080220165513.GU4539@artesyncp.com \
--to=stephane.chazelas@emerson.com \
--cc=arnd@arndb.de \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 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.