From: Robin Murphy <robin.murphy@arm.com>
To: "Markus Elfring" <Markus.Elfring@web.de>,
iommu@lists.linux.dev, kernel-janitors@vger.kernel.org,
"Jörg Rödel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: iommu/ipmmu-vmsa: Use devm_platform_get_and_ioremap_resource() in ipmmu_probe()
Date: Mon, 5 Feb 2024 14:00:57 +0000 [thread overview]
Message-ID: <f27d7b45-89d9-4b5c-9bde-806b57bbe8e7@arm.com> (raw)
In-Reply-To: <0c757d69-ec60-477c-a978-a94118a571a2@web.de>
On 2024-02-05 1:02 pm, Markus Elfring wrote:
>>>>> Thus reuse existing functionality instead of keeping duplicate source code.
>>>>
>>>> Much as I detest the get_and_ioremap_resource obfuscator, it's not even appropriate here since nothing else is using "res".
>>>
>>> I got the impression that this local variable is needed to perform
>>> a desired function call.
>>
>> Yes, the call to devm_ioremap_resource(). Which you're proposing to remove...
>
> I propose to replace a specific function call combination
> by an other single call for a known wrapper function.
> The mentioned variable is preserved for this purpose.
No. If you believe in cleaning up code, please apply your brain and
clean up code *meaningfully* - others seem to have managed it just fine
(e.g. [1][2] at random from a quick search on lore). Hell, I think even
the original now-deleted script could auto-generate a proper patch for
situations where devm_platform_ioremap_resource() was appropriate -
there is zero excuse for doing a *worse* job 4 years later.
If on the other hand your interest is not to actually clean up the code
for the good of the community, but to stoke your own ego as a
"contributor" of shitty patches that annoy people and reinforce the
popular impression that you are in fact an AI, please stop, or at the
very least please refrain from doing so in any areas I review or maintain.
Thanks,
Robin.
[1] https://lore.kernel.org/all/20191013152716.1830911-1-jic23@kernel.org/
[2]
https://lore.kernel.org/all/20200412135023.3831-1-aishwaryarj100@gmail.com/
next prev parent reply other threads:[~2024-02-05 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 10:42 [PATCH] " Markus Elfring
2024-02-05 11:11 ` Robin Murphy
2024-02-05 11:52 ` Markus Elfring
2024-02-05 12:34 ` Robin Murphy
2024-02-05 13:02 ` Markus Elfring
2024-02-05 14:00 ` Robin Murphy [this message]
2024-02-05 18:29 ` Markus Elfring
2024-02-06 14:15 ` [PATCH v2] iommu/ipmmu-vmsa: Use devm_platform_ioremap_resource() " Markus Elfring
2024-02-07 9:13 ` Geert Uytterhoeven
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=f27d7b45-89d9-4b5c-9bde-806b57bbe8e7@arm.com \
--to=robin.murphy@arm.com \
--cc=Markus.Elfring@web.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®