[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250911-crystal-dexterous-ostrich-fcdf3c@lemur>
Date: Thu, 11 Sep 2025 09:50:31 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Vikram Sharma <quic_vikramsa@...cinc.com>, bryan.odonoghue@...aro.org, mchehab@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, andersson@...nel.org,
konradybcio@...nel.org, hverkuil-cisco@...all.nl, cros-qcom-dts-watchers@...omium.org,
catalin.marinas@....com, will@...nel.org, linux-arm-kernel@...ts.infradead.org,
quic_svankada@...cinc.com, linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Nihal Kumar Gupta <quic_nihalkum@...cinc.com>
Subject: Re: [PATCH v3.1] media: dt-bindings: Add qcom,qcs8300-camss
compatible
On Wed, Sep 10, 2025 at 02:25:30PM +0200, Konrad Dybcio wrote:
> > Please version your patches correctly, e.g. use b4 or git format-patch
> > -vX, and add changelog in cover letter or under '---' of individual
> > patches describing changes from previous version.
> >
> > What is v3.1? How to compare it? Try yourself:
>
> This is a weird invention that some media maintainers seem to promote..
Please tell them to stop. Patch revisions are not supposed to follow any kind
of semver. It's a new version of a patch and it should always be a simple full
integer increment.
> As a b4 user, I would also like it to stop, as doing anything other than
> v(integer) will open the door for unlimited craziness
To my knowledge, no tooling will do the right thing with that -- b4,
patchwork, patchew, etc. It's needlessly complicating things.
-K
Powered by blists - more mailing lists