From: Stephen Boyd <sboyd@codeaurora.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [GIT PULL] clk: ti: clkctrl support for 4.13 merge window
Date: Wed, 14 Jun 2017 10:32:37 -0700 [thread overview]
Message-ID: <20170614173237.GB20170@codeaurora.org> (raw)
In-Reply-To: <6d66f78a-5d39-6396-c492-b79a687ce58a@ti.com>
On 06/08, Tero Kristo wrote:
> Hi Stephen, Mike,
>
> This pull contains the v3 of the clkctrl base driver support posted
> couple of weeks back, with Tony's acks added to patch #2 and #4.
>
> -Tero
>
drivers/clk/ti/clkctrl.c:252
_ti_clkctrl_clk_register() warn: possible memory leak of 'clkctrl_clk'
drivers/clk/ti/clkctrl.c:264
_ti_clkctrl_clk_register() warn: possible memory leak of 'clkctrl_clk'
drivers/clk/ti/clkctrl.c:466
_ti_omap4_clkctrl_setup() warn: possible memory leak of 'clkctrl_clk'
drivers/clk/ti/clkctrl.c:473
_ti_omap4_clkctrl_setup() warn: possible memory leak of 'clkctrl_clk'
Can these be silenced with some follow up patch? I'll hold off on
the pull until you can take a look.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-14 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 14:51 [GIT PULL] clk: ti: clkctrl support for 4.13 merge window Tero Kristo
2017-06-14 17:32 ` Stephen Boyd [this message]
2017-06-14 17:40 ` Tero Kristo
2017-06-14 17:49 ` Stephen Boyd
2017-06-15 8:12 ` Tero Kristo
2017-06-16 21:59 ` Stephen Boyd
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=20170614173237.GB20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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 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).