From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-tegra@vger.kernel.org, linux-mtd@lists.infradead.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Lucas Stach <dev@lynxeye.de>,
Richard Weinberger <richard@nod.at>,
Stefan Agner <stefan@agner.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, Qasim Ijaz <qasdev00@gmail.com>,
Natalie Vock <natalie.vock@gmx.de>
Subject: Re: [PATCH] mtd: rawnand: tegra: Simplify maximum determination in tegra_nand_setup_timing()
Date: Mon, 03 Mar 2025 11:43:04 +0100 [thread overview]
Message-ID: <87pliy9yyv.fsf@bootlin.com> (raw)
In-Reply-To: <d564cafe-d45a-40b5-9a91-a2e2b97c80d6@web.de> (Markus Elfring's message of "Fri, 28 Feb 2025 19:33:10 +0100")
Hi,
On 28/02/2025 at 19:33:10 +01, Markus Elfring <Markus.Elfring@web.de> wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Fri, 28 Feb 2025 19:19:45 +0100
>
> Reduce nested max() calls by a single max3() call in this
> function implementation.
>
> The source code was transformed by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
I am sorry, I do not see what gets simplified. max(max(a,b),max(c,d))
looks simpler than max3(a,b,max(c,d)). Does it bring something in terms
of optimization?
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-03-03 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 18:33 [PATCH] mtd: rawnand: tegra: Simplify maximum determination in tegra_nand_setup_timing() Markus Elfring
2025-03-03 10:43 ` Miquel Raynal [this message]
2025-03-03 10:55 ` Markus Elfring
2025-03-03 11:03 ` Miquel Raynal
2025-03-03 11:15 ` Markus Elfring
2025-03-03 11:25 ` Miquel Raynal
2025-03-04 15:09 ` Miquel Raynal
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=87pliy9yyv.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Markus.Elfring@web.de \
--cc=dev@lynxeye.de \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=natalie.vock@gmx.de \
--cc=qasdev00@gmail.com \
--cc=richard@nod.at \
--cc=stefan@agner.ch \
--cc=thierry.reding@gmail.com \
--cc=vigneshr@ti.com \
/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 NNTP newsgroup(s).