DMA Engine development
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "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 09:47:45 +0100	[thread overview]
Message-ID: <7332ccd2-ebe6-4b9d-a2ae-8f33641e7bd4@web.de> (raw)
In-Reply-To: <7064597b-caf7-42e2-b083-b3531e874200@prolan.hu>

>>> Clean up error handling by using devm functions and dev_err_probe().
>> …
>>
>> Do any contributors care for a different patch granularity?
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14#n81
>
> I still don't understand why you are so adamant on this.

There are developers who tend to prefer an other change granularity.


> It is just a simple refactor patch changing 33 lines,

The transformation goal is fine.


> mostly in one function, with no logic change.

Implementation details are probably worth for another look.


> Does it break something in your system? Please explain yourself so we can understand your viewpoint better.

I hope that the understanding can grow also for another bit of refinement.


>> Will it be clearer to mention also the function name “sun4i_dma_probe”
>> in the summary phrases?
>
> I already added it as per your last response, did you not read the message?
>
> On 2025. 03. 24. 18:20, Bence Csókás wrote:
>> Clean up error handling by using devm functions and dev_err_probe(). This
>> should make it easier to add new code, as we can eliminate the "goto
>> ladder" in sun4i_dma_probe().
Please distinguish better between information from the “changelog”
and items in a message subject.

Regards,
Markus

  reply	other threads:[~2025-03-25  8:48 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     ` Markus Elfring [this message]
2025-03-25  8:58       ` [v6] " 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
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=7332ccd2-ebe6-4b9d-a2ae-8f33641e7bd4@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=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