From: Brian Norris <computersforpeace@gmail.com>
To: Martin Habets <mhabets@solarflare.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtdcore: Infrastructure for the device release API
Date: Fri, 26 May 2017 17:13:23 -0700 [thread overview]
Message-ID: <20170527001323.GF114788@google.com> (raw)
In-Reply-To: <20170518092248.23934.15034.stgit@mh-desktop.uk.solarflarecom.com>
On Thu, May 18, 2017 at 10:23:11AM +0100, Martin Habets wrote:
> This API adds a cleanup callback for the user of an MTD device.
> Normally they will have allocated the mtd_info structure, and using
> this callback they can free that memory when the last reference is
> dropped.
Can you provide an example user? This callback is meaningless (and won't
be merged) if it has no users.
> CONFIG_DEBUG_KOBJECT_RELEASE can be used to detect users that free
> the memory too early.
Are there any such users?
> The information contained in this message is confidential and is
> intended for the addressee(s) only. If you have received this message
> in error, please notify the sender immediately and delete the message.
> Unless you are an addressee (or authorized to receive for an
> addressee), you may not use, copy or disclose to anyone this message
> or any information contained in this message. The unauthorized use,
> disclosure, copying or alteration of this message is strictly
> prohibited.
Nice.
Brian
next prev parent reply other threads:[~2017-05-27 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:23 [PATCH] mtdcore: Infrastructure for the device release API Martin Habets
2017-05-27 0:13 ` Brian Norris [this message]
2017-05-31 16:15 ` Martin Habets
2017-06-22 13:54 ` Martin Habets
2017-07-08 1:47 ` Brian Norris
2017-07-18 15:51 ` Martin Habets
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=20170527001323.GF114788@google.com \
--to=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mhabets@solarflare.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 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.