From: "Liang He" <windhl@126.com>
To: "Stephen Boyd" <sboyd@kernel.org>, Conor.Dooley@microchip.com
Cc: jonathanh@nvidia.com, mturquette@baylibre.com,
pdeschrijver@nvidia.com, pgaikwad@nvidia.com,
thierry.reding@gmail.com, linux-clk@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v2] clk: tegra: (clk-tegra30) Add missing of_node_put()
Date: Thu, 16 Jun 2022 16:19:41 +0800 (CST) [thread overview]
Message-ID: <1a776c99.5e5c.1816b98bfee.Coremail.windhl@126.com> (raw)
In-Reply-To: <20220616060037.5AEB8C34114@smtp.kernel.org>
At 2022-06-16 14:00:35, "Stephen Boyd" <sboyd@kernel.org> wrote:
>The subject should match historical subjects
>
> $ git log --oneline -3 -- drivers/clk/tegra/clk-tegra30.c
>
>shows mostly "clk: tegra: ". Can you also combine this with the other
>tegra patch? Don't think we need two patches for essentially the same
>thing.
>
>Quoting Liang He (2022-06-15 20:36:22)
>> In tegra30_clock_init, of_find_matching_node() will return a node
>> pointer with refcount incremented. We should use of_node_put() when
>> the node pointer is not used anymore.
>>
>> Signed-off-by: Liang He <windhl@126.com>
>> ---
>> changelog:
>>
>> v2: use real name for Sob
>
>Thanks!
>
>> v1: fix missing bug
Sorry for my fault. I have been advised to use real name and I resend a PATCH v2 with my real name, but really with the same patch code.
So how can I withdraw the first patch or resend other thing? I am confused.
Can you help me, Conor?
next prev parent reply other threads:[~2022-06-16 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 3:36 [PATCH v2] clk: tegra: (clk-tegra30) Add missing of_node_put() Liang He
2022-06-16 6:00 ` Stephen Boyd
2022-06-16 8:19 ` Liang He [this message]
2022-06-16 8:42 ` Conor.Dooley
2022-06-16 9:09 ` Liang He
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=1a776c99.5e5c.1816b98bfee.Coremail.windhl@126.com \
--to=windhl@126.com \
--cc=Conor.Dooley@microchip.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.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