linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Jian Dong <dj0227@163.com>
Cc: abel.vesa@nxp.com, mturquette@baylibre.com,
	s.hauer@pengutronix.de, shawnguo@kernel.org, linux-imx@nxp.com,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, huyue2@yulong.com,
	Jian Dong <dongjian@yulong.com>
Subject: Re: [PATCH]  clk: imx: reference preceded by free
Date: Thu, 08 Apr 2021 00:41:18 -0700	[thread overview]
Message-ID: <161786767850.3790633.2996848068001353291@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210408095312.00004267@163.com>

Quoting Jian Dong (2021-04-07 18:53:12)
> On Tue, 30 Mar 2021 19:16:48 -0700
> Stephen Boyd <sboyd@kernel.org> wrote:
> 
> > Quoting Jian Dong (2021-03-22 20:10:34)
> > > From: Jian Dong <dongjian@yulong.com>
> > > 
> > >  when register failed, clk will be freed, it will generate dangling
> > > pointer problem in later reference. it should return directly.
> > > 
> > > Signed-off-by: Jian Dong <dongjian@yulong.com>
> > > ---  
> > 
> > Any Fixes tag?
> 
> Sorry for late, I'm unfamiliar with tag rule.
> 
> For this patch include two files commit 2f77296d3 and fe37b482
> maybe likes:
> 
> Fixes: 2f77296d3        (clk: imx: add lpcg clock support)
> Fixes: fe37b482         (clk: imx: add scu clock common part)
> 
> and I noticed this patch has been merged, do I need RESEND again with
> tags like above?
> 

Looks like Abel already picked it up so no need to resend.

      reply	other threads:[~2021-04-08  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  3:10 [PATCH] clk: imx: reference preceded by free Jian Dong
2021-03-30  9:17 ` Abel Vesa
2021-03-31  2:16 ` Stephen Boyd
2021-04-08  1:53   ` Jian Dong
2021-04-08  7:41     ` Stephen Boyd [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=161786767850.3790633.2996848068001353291@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=abel.vesa@nxp.com \
    --cc=dj0227@163.com \
    --cc=dongjian@yulong.com \
    --cc=huyue2@yulong.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).