linux-kernel - Re: [PATCH v2 01/41] drm/tests: Order Kunit tests in Makefile

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220831121949.xj2bdykhvs3cvvm7@meerkat.local>
Date:   Wed, 31 Aug 2022 08:19:49 -0400
From:   Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To:     Maxime Ripard <maxime@...no.tech>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 01/41] drm/tests: Order Kunit tests in Makefile

On Wed, Aug 31, 2022 at 09:30:26AM +0200, Maxime Ripard wrote:
> Another thing I noticed when using b4 send is that I'm not sure how to
> increment the version number of a series. With b4 send --dry-run it
> wasn't happening automatically, and I couldn't find anything related in
> the options (except for --force-revision but that wasn't permanent I
> think?)

It is, but I don't blame you being confused seeing as there's no documentation
yet at this point. :) I hope to make some final changes to flags and features
in the near future, so documentation should start appearing soon.

> I ended up amending the commit json by hand to set the proper revision
> number, but I'm almost sure it isn't the right way :)

This is certainly a valid way to go about it as well.

Regards,
-K