From: Dragan Simic <dsimic@manjaro.org>
To: Andrey Leonchikov <andreil499@gmail.com>
Cc: linux-rockchip@lists.infradead.org
Subject: Re: [v2,PATCH 5/5] RK356x - Add OTP description.
Date: Sat, 13 Sep 2025 16:58:52 +0200 [thread overview]
Message-ID: <36fbeabf43ffab99255061512073f70e@manjaro.org> (raw)
In-Reply-To: <20250912124945.2300498-1-andreil499@gmail.com>
Hello Andrey,
On 2025-09-12 14:49, Andrey Leonchikov wrote:
> Ok, I will work on this patches a more and send a v3 soon.
> About v1 - I immediatelly archive it - this messages don't have any
> descriptions.
I'm sorry, but that's not the way the patch versioning works.
When you send patches to mailing lists, the version numbers refer
to the versions sent to the mailing list, instead of referring
to your internal patch versions.
Thus, the first version sent to a mailing list cannot be v2.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2025-09-13 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 21:54 [v2,PATCH 0/5] RK3566 BigtreeTech Pi2 fixes Andrey Leonchikov
2025-09-10 21:54 ` [v2,PATCH 1/5] RK3566 BTT Pi2 DTS fixes Andrey Leonchikov
2025-09-10 21:54 ` [v2,PATCH 2/5] RK3566 BTT Pi2 - Fix GMAC default delays Andrey Leonchikov
2025-09-12 15:06 ` Jonas Karlman
2025-09-10 21:54 ` [v2,PATCH 3/5] RK3566 BTT Pi2 - Fix RK808 clock names. Require for a normal shutdown/reboot Andrey Leonchikov
2025-09-10 21:54 ` [v2,PATCH 4/5] RK3566 BTT Pi2 - Fix default values Andrey Leonchikov
2025-09-10 21:54 ` [v2,PATCH 5/5] RK356x - Add OTP description Andrey Leonchikov
2025-09-12 10:45 ` Dragan Simic
2025-09-12 12:49 ` Andrey Leonchikov
2025-09-13 14:58 ` Dragan Simic [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=36fbeabf43ffab99255061512073f70e@manjaro.org \
--to=dsimic@manjaro.org \
--cc=andreil499@gmail.com \
--cc=linux-rockchip@lists.infradead.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