public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	linux-tegra@vger.kernel.org, linux-mtd@lists.infradead.org
Cc: 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: mtd: rawnand: tegra: Simplify maximum determination in tegra_nand_setup_timing()
Date: Mon, 3 Mar 2025 12:15:25 +0100	[thread overview]
Message-ID: <10afda2a-4c52-47a8-bdfd-4bfd7bd9cb34@web.de> (raw)
In-Reply-To: <87h64a9y04.fsf@bootlin.com>

>> You would eventually like to express that a maximum should be determined
>> from three (or even four?) values.
>
> If there was a max4(), why not, but in this case I don't see the point.
Do you miss such a programming interface so far?
Would you be looking for corresponding software adjustments?

Regards,
Markus

  reply	other threads:[~2025-03-03 11:15 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
2025-03-03 10:55   ` Markus Elfring
2025-03-03 11:03     ` Miquel Raynal
2025-03-03 11:15       ` Markus Elfring [this message]
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=10afda2a-4c52-47a8-bdfd-4bfd7bd9cb34@web.de \
    --to=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=miquel.raynal@bootlin.com \
    --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