public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-gpio@vger.kernel.org, Axel Lin <axel.lin@ingics.com>
Subject: re: pinctrl: mediatek: emulate GPIO interrupt on both-edges
Date: Fri, 13 Mar 2015 21:48:38 +0800	[thread overview]
Message-ID: <1426254518.16768.317.camel@mtksdaap41> (raw)
In-Reply-To: <20150313083824.GA5750@mwanda>

On Fri, 2015-03-13 at 11:38 +0300, Dan Carpenter wrote:
> Hello Yingjoe Chen,
> 
> The patch c3a785c1b041: "pinctrl: mediatek: emulate GPIO interrupt on
> both-edges" from Jan 27, 2015, leads to the following static checker
> warning:
> 
> 	drivers/pinctrl/mediatek/pinctrl-mtk-common.c:1252 mtk_pctrl_init()
> 	warn: passing devm_ allocated variable to kfree. 'pctl->eint_dual_edges'

Hi,

Thanks for catching this. It seems Axel already post a fix for me:

http://article.gmane.org/gmane.linux.kernel.gpio/6789

Joe.C



      reply	other threads:[~2015-03-13 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  8:38 pinctrl: mediatek: emulate GPIO interrupt on both-edges Dan Carpenter
2015-03-13 13:48 ` Yingjoe Chen [this message]

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=1426254518.16768.317.camel@mtksdaap41 \
    --to=yingjoe.chen@mediatek.com \
    --cc=axel.lin@ingics.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-gpio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox