From: Markus Elfring <Markus.Elfring@web.de>
To: "Julian Calaby" <julian.calaby@gmail.com>,
"Csókás Bence" <csokas.bence@prolan.hu>,
dmaengine@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Chen-Yu Tsai <wens@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [v6] dma-engine: sun4i: Simplify error handling in probe()
Date: Tue, 25 Mar 2025 13:38:57 +0100 [thread overview]
Message-ID: <77fbff4c-443d-4ed4-8335-a6cbec6b2809@web.de> (raw)
In-Reply-To: <CAGRGNgU7t85oG3Bq7L3KjKUAbRyd6SHSM6F6BvmdXDVkbNegKg@mail.gmail.com>
> You're "concerned" about patch granularity, but this is not the sort
> of thing that some random person would raise, this is the sort of
> thing a maintainer asks for when patches are doing too many things or
> are unreviewable. …
May additional patch reviewers influence the software evolution another bit?
…
>>> What do you mean? …
…
> Once again your comments are just noise, and your insistence on
> repeating them over and over and over and over and over again is
> borderline harassment.
Some information needs to be repeated also according to known communication difficulties.
Corresponding views might be evolving further.
…
> Please block or ignore Markus, at best he's a nuisance and at worst a troll.
I hope that development discussions can become more constructive again.
Regards,
Markus
next prev parent reply other threads:[~2025-03-25 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:20 [PATCH v6] dma-engine: sun4i: Simplify error handling in probe() Bence Csókás
2025-03-24 17:55 ` Markus Elfring
2025-03-25 8:26 ` Csókás Bence
2025-03-25 8:47 ` [v6] " Markus Elfring
2025-03-25 8:58 ` Csókás Bence
2025-03-25 9:12 ` Markus Elfring
2025-03-25 12:20 ` Julian Calaby
2025-03-25 12:38 ` Markus Elfring [this message]
2025-03-25 12:39 ` Csókás Bence
2025-03-25 13:04 ` Julian Calaby
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=77fbff4c-443d-4ed4-8335-a6cbec6b2809@web.de \
--to=markus.elfring@web.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=csokas.bence@prolan.hu \
--cc=dmaengine@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=julian.calaby@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=vkoul@kernel.org \
--cc=wens@csie.org \
--cc=wens@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