From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-i2c@vger.kernel.org, Axel Lin <axel.lin@ingics.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] i2c: versatile: Convert to use resource managed devm_* APIs
Date: Fri, 8 Jul 2016 14:44:17 +0100 [thread overview]
Message-ID: <20160708134417.GF3784@red-moon> (raw)
In-Reply-To: <1467640573.23717.3.camel@arm.com>
On Mon, Jul 04, 2016 at 02:56:13PM +0100, Pawel Moll wrote:
> Dnia 2016-06-25, Sat o godzinie 09:41 +0800, Axel Lin pisze:
> > 2016-04-14 22:31 GMT+08:00 Axel Lin <axel.lin@ingics.com>:
> > > Use devm_* APIs to simplify the code a bit.
> > > This patch also fixes the memory leak when unload the module.
> > >
> > > Signed-off-by: Axel Lin <axel.lin@ingics.com>
> > > ---
> > > Hi,
> > > I don't have this h/w, I'd appreciate if someone can test this
> > > patch.
> >
> > Obviously the module unload path has memory leak.
> > Just wondering if anyone can review/test this patch.
>
> Gentlemen? (referring to the VE maintainers here)
>
> Original thread: thread.gmane.org/gmane.linux.drivers.i2c/27277
We weren't CC'ed, thanks for the heads-up anyway we will have a
look and test shortly (@Axel next time please CC us if you want
us to test your patches, thanks).
Lorenzo
prev parent reply other threads:[~2016-07-08 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:30 [PATCH 1/2] i2c: versatile: Allow compile test build Axel Lin
2016-04-14 14:31 ` [PATCH 2/2] i2c: versatile: Convert to use resource managed devm_* APIs Axel Lin
2016-06-25 1:41 ` Axel Lin
2016-07-04 13:56 ` Pawel Moll
2016-07-08 13:44 ` Lorenzo Pieralisi [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=20160708134417.GF3784@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=axel.lin@ingics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=pawel.moll@arm.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sudeep.holla@arm.com \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).