From: avkrasnov at rulkc.org (Arseniy Krasnov)
Subject: [rulkc] [PATCH v1] mtd: rawnand: fix condition in 'nand_select_target()'
Date: Tue, 05 May 2026 14:46:21 +0300 [thread overview]
Message-ID: <e7e7b46c-70a1-48b9-a2be-57080556fb65@rulkc.org> (raw)
In-Reply-To: <87bjeuqn6s.fsf@bootlin.com>
05.05.2026 11:23, Miquel Raynal wrote:
> On 05/05/2026 at 11:14:25 +03, Arseniy Krasnov <avkrasnov at rulkc.org> wrote:
>
>> 05.05.2026 11:10, Miquel Raynal wrote:
>>> On 05/05/2026 at 10:59:16 +03, Arseniy Krasnov <avkrasnov at rulkc.org> wrote:
>>>
>>>> 05.05.2026 10:50, Miquel Raynal wrote:
>>>>> Hi,
>>>>>
>>>>> On 05/05/2026 at 01:10:12 +03, Arseniy Krasnov <avkrasnov at rulkc.org> wrote:
>>>>>
>>>>> Two important typos in the commit log :-)
>>>>>
>>>>>> 'cs' here must in range [0:nanddev_ntargets).
>>>>> be [
>>>> Hi, sorry, You mean?
>>>>
>>>>
>>>> 'cs' here must be in range [0:nanddev_ntargets].
>>> I meant [0:nanddev_ntargets[ which is the mathematical way, IIRC, to
>>> indicate that the last value is out of scope/excluded.
>>>
>>> [0:nanddev_ntargets] means that nanddev_ntargets is included in the
>>> scope of values and here since you are explicitly showing that it is
>>> not, it feels wrong to use that convention.
>>
>> Ahh, Yes I see, just small misunderstood in math symbols:
>>
>> I mean: [A:B) == [A:B[
>>
>> https://wikimedia.org/api/rest_v1/media/math/render/svg/0719b1b08cdf649e735e6dab6dc7355fa37a9b21
> Ah ok, didn't know that other convention, fine then, take the one you prefer if
> both are identical. Just add the missing "be" please!
Sure!
Thanks, Arseniy
>
> Thanks,
> Miquèl
prev parent reply other threads:[~2026-05-05 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 22:10 avkrasnov
2026-05-05 7:50 ` miquel.raynal
2026-05-05 7:59 ` avkrasnov
2026-05-05 8:10 ` miquel.raynal
2026-05-05 8:14 ` avkrasnov
2026-05-05 8:23 ` miquel.raynal
2026-05-05 11:46 ` avkrasnov [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=e7e7b46c-70a1-48b9-a2be-57080556fb65@rulkc.org \
--to=rulkc@linuxtesting.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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®