All of lore.kernel.org
 help / color / mirror / Atom feed
From: JeffyChen <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 2/3] regmap: debugfs: Fix kmemleak in regmap_debugfs_init
Date: Wed, 07 Mar 2018 18:56:17 +0800	[thread overview]
Message-ID: <5A9FC551.5090909@rock-chips.com> (raw)
In-Reply-To: <20180306125916.GA13586@sirena.org.uk>

Hi Mark,

Thanks for your reply.

On 03/06/2018 08:59 PM, Mark Brown wrote:
> On Tue, Mar 06, 2018 at 07:04:02PM +0800, Jeffy Chen wrote:
>> Use map->debugfs_name to store allocated debugfs name, so it would be
>> freed in regmap_debugfs_exit().
>
> I'm missing patch 1 in this series and I think this collides with a fix
> I already have locally.
>
sorry for that, i should CC you the whole seires.

the patch 1 should be:
https://patchwork.kernel.org/patch/10261413

  reply	other threads:[~2018-03-07 10:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 11:04 [PATCH v2 1/3] mfd: syscon: Set name of regmap_config Jeffy Chen
2018-03-06 11:04 ` [PATCH v2 2/3] regmap: debugfs: Fix kmemleak in regmap_debugfs_init Jeffy Chen
2018-03-06 12:59   ` Mark Brown
2018-03-07 10:56     ` JeffyChen [this message]
2018-03-06 11:04 ` [PATCH v2 3/3] regmap: debugfs: Free map->debugfs_name when debugfs_create_dir() failed Jeffy Chen
2018-03-07 14:15   ` Applied "regmap: debugfs: Free map->debugfs_name when debugfs_create_dir() failed" to the regmap tree Mark Brown
2018-03-06 14:58 ` [PATCH v2 1/3] mfd: syscon: Set name of regmap_config JeffyChen
2018-03-07 10:20   ` Mark Brown
2018-03-07 10:50     ` JeffyChen
2018-03-07 10:57       ` Mark Brown
2018-03-07 16:54         ` Lee Jones
2018-03-07 16:57           ` Mark Brown
2018-03-12 14:07             ` Lee Jones
2018-03-12 16:11               ` Mark Brown

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=5A9FC551.5090909@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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.