From: Jamie Iles <jamie@jamieiles.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Sudhakar Rajashekhara <sudhakar.raj@ti.com>,
Jamie Iles <jamie@jamieiles.com>,
David Woodhouse <David.Woodhouse@intel.com>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: denali: remove calling mtd_device_unregister() after nand_release()
Date: Fri, 3 Jun 2011 10:20:57 +0100 [thread overview]
Message-ID: <20110603092057.GC2637@pulham.picochip.com> (raw)
In-Reply-To: <1307063535.10001.1.camel@phoenix>
On Fri, Jun 03, 2011 at 09:12:15AM +0800, Axel Lin wrote:
> The implementation of nand_release() already call mtd_device_unregister(),
> no need to call it again.
Good catch!
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Acked-by: Jamie Iles <jamie@jamieiles.com>
next prev parent reply other threads:[~2011-06-03 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 1:12 [PATCH] mtd: denali: remove calling mtd_device_unregister() after nand_release() Axel Lin
2011-06-03 9:20 ` Jamie Iles [this message]
2011-06-06 10:07 ` Artem Bityutskiy
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=20110603092057.GC2637@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=David.Woodhouse@intel.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sudhakar.raj@ti.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