From: Marco Nenciarini <mnencia@kcore.it>
To: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com
Cc: bingbu.cao@intel.com, tian.shu.qiu@intel.com, mchehab@kernel.org,
stable@vger.kernel.org, andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH v2] media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges
Date: Wed, 1 Apr 2026 18:25:31 +0200 [thread overview]
Message-ID: <ac1G-zhysXIJcOO9@spark.kcore.it> (raw)
In-Reply-To: <ac0BVwO4XGhzcMu3@kekkonen.localdomain>
Hi Sakari,
Thanks for the review. All three points addressed in v3.
On the exact default_mbps match: yes, the range check covers it
since default_mbps always falls within [min, max] for every entry,
so the early return was redundant.
On the early exit: I adopted your suggestion to use separate
continue/break, but swapped the two. Since both min and max
increase monotonically through the table, mbps > max needs to
continue (later entries have higher max) while mbps < min can
break (no later entry can match).
Marco
prev parent reply other threads:[~2026-04-01 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260323154037.1404865-1-mnencia@kcore.it>
2026-03-25 9:32 ` [PATCH v2] media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges Marco Nenciarini
2026-04-01 7:11 ` Marco Nenciarini
2026-04-01 11:28 ` Sakari Ailus
2026-04-01 16:25 ` Marco Nenciarini [this message]
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=ac1G-zhysXIJcOO9@spark.kcore.it \
--to=mnencia@kcore.it \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tian.shu.qiu@intel.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