From: Dan Carpenter <dan.carpenter@linaro.org>
To: Fei Shao <fshao@chromium.org>
Cc: Markus Elfring <Markus.Elfring@web.de>,
Jerome Brunet <jbrunet@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [PATCH] clk: Fix memory leak in devm_clk_notifier_register()
Date: Mon, 19 Jun 2023 08:27:51 +0300 [thread overview]
Message-ID: <8366a35f-bc2c-4aee-b2bb-5fc9b2a7072b@kadam.mountain> (raw)
In-Reply-To: <CAC=S1ngN=TFQa0Y4FoSCOTUs8HRi4NEP1OwY8WccUEUMG_UDeQ@mail.gmail.com>
On Mon, Jun 19, 2023 at 11:56:56AM +0800, Fei Shao wrote:
> On Sun, Jun 18, 2023 at 4:06 AM Markus Elfring <Markus.Elfring@web.de> wrote:
> >
> > > This fixes the issue.
> >
> > Please replace this sentence by an imperative change suggestion.
> >
> > See also:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.4-rc6#n94
> >
> > Regards,
> > Markus
>
> Thanks for the feedback. I just sent v2.
Markus is banned from vger lists... He doesn't have a very accurate
perspective of what is important and what is not important.
regards,
dan carpenter
next prev parent reply other threads:[~2023-06-19 5:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 8:09 [PATCH] clk: Fix memory leak in devm_clk_notifier_register() Fei Shao
[not found] ` <71168ceb-8273-4067-d0e0-c6c219d4618e@web.de>
2023-06-19 3:56 ` Fei Shao
2023-06-19 5:27 ` Dan Carpenter [this message]
[not found] ` <ea5c0b0b-7aa5-d4eb-def9-fa279d69cd44@web.de>
2023-06-19 8:32 ` Dan Carpenter
[not found] ` <6e1071ec-f19a-454c-215a-b5193984bc6b@web.de>
2023-06-19 9:30 ` Dan Carpenter
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=8366a35f-bc2c-4aee-b2bb-5fc9b2a7072b@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=fshao@chromium.org \
--cc=jbrunet@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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