All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: <linux-mtd@lists.infradead.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 0/3] mtd: support cleanup callback for partition parsers
Date: Thu, 19 Nov 2015 19:26:34 -0800	[thread overview]
Message-ID: <1447989997-108476-1-git-send-email-computersforpeace@gmail.com> (raw)

Hi,

Currently, we assume that all of the resources used by partition parsers can be
cleaned up with a single kfree(), but that can be burdensome to work around.
This series (particularly, patch 3) supports a cleanup() callback for parsers.

Brian

Brian Norris (3):
  mtd: rename MTD parser get/put
  mtd: untangle error codes and number of partitions
  mtd: support a cleanup callback for partition parsers

 drivers/mtd/mtdcore.c          | 22 ++++++++++++++++------
 drivers/mtd/mtdcore.h          | 25 ++++++++++++++++++++++++-
 drivers/mtd/mtdpart.c          | 19 +++++++++++--------
 include/linux/mtd/partitions.h |  1 +
 4 files changed, 52 insertions(+), 15 deletions(-)

-- 
2.6.0.rc2.230.g3dd15c0

             reply	other threads:[~2015-11-20  3:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20  3:26 Brian Norris [this message]
2015-11-20  3:26 ` [PATCH 1/3] mtd: rename MTD parser get/put Brian Norris
2015-11-30 17:55   ` Boris Brezillon
2015-11-20  3:26 ` [PATCH 2/3] mtd: untangle error codes and number of partitions Brian Norris
2015-11-30 17:56   ` Boris Brezillon
2015-11-20  3:26 ` [PATCH 3/3] mtd: support a cleanup callback for partition parsers Brian Norris
2015-11-30 18:36   ` Boris Brezillon
2015-11-30 23:53     ` Brian Norris
2015-12-01 12:37       ` Boris Brezillon
2015-12-02  3:12         ` Brian Norris
2015-12-02  8:55           ` Boris Brezillon

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=1447989997-108476-1-git-send-email-computersforpeace@gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linus.walleij@linaro.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.