From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <dan.carpenter@linaro.org>,
kernel-janitors@vger.kernel.org
Cc: Fei Shao <fshao@chromium.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [cocci] clk: Fix memory leak in devm_clk_notifier_register()
Date: Mon, 19 Jun 2023 11:57:14 +0200 [thread overview]
Message-ID: <0ec93feb-221a-c10b-289c-6e787b232b51@web.de> (raw)
In-Reply-To: <8352fe9a-f76d-4ddb-aec4-d2c443f2fb2a@kadam.mountain>
> Markus you always answer every email with more questions instead of
> just listening to what I am saying.
Additional input triggers further clarification opportunities.
> This is why you were banned.
I guess that various factors were involved for this historic action.
> Even though you are banned, I encourage people to merge your patches
> if they fix bugs. And if your review comments are about bugs then they
> are welcome.
Thanks for another bit of positive feedback.
> If they are about coding style or grammar then they are distracting.
Such items belong also to patch review approaches.
> I know that you are going to ask more questions
Some developers and code reviewers are used to such a habit.
> but I am not going to respond further.
Constructive responses can evolve also according to various change possibilities
(which are still in waiting queues).
Regards,
Markus
prev parent reply other threads:[~2023-06-19 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230617160901.1.I2b151cdf7a72d9e3ecc7ab2ff38409ebe6d65d6b@changeid>
2023-06-17 20:00 ` [cocci] [PATCH] clk: Fix memory leak in devm_clk_notifier_register() Markus Elfring
[not found] ` <CAC=S1ngN=TFQa0Y4FoSCOTUs8HRi4NEP1OwY8WccUEUMG_UDeQ@mail.gmail.com>
[not found] ` <8366a35f-bc2c-4aee-b2bb-5fc9b2a7072b@kadam.mountain>
2023-06-19 7:42 ` [cocci] " Markus Elfring
[not found] ` <56998d04-7f09-4982-b0f1-20ef917aa524@kadam.mountain>
2023-06-19 9:11 ` Markus Elfring
[not found] ` <8352fe9a-f76d-4ddb-aec4-d2c443f2fb2a@kadam.mountain>
2023-06-19 9:57 ` Markus Elfring [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=0ec93feb-221a-c10b-289c-6e787b232b51@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=dan.carpenter@linaro.org \
--cc=fshao@chromium.org \
--cc=jbrunet@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).