Re: [PATCH] vadidation: add used-to-be-signed unit tests

[Vincent Mailhol <mailhol@kernel.org>]

On 24/09/2025 at 16:03, Chris Li wrote:
> On Mon, Sep 22, 2025 at 8:54 AM Vincent Mailhol <mailhol@kernel.org> wrote:
>>
>> Add unit tests for the new used-to-be-signed check as introduced in [1]:
> 
> Applied and pushed on sparse-dev repo. Can you please take a look if I
> am doing it correctly on the sparse-dev?

I just checked out sparse-dev. I re-run the tests and everything looks fine!

> Linus has one more debug print line, can you add it for me and submit
> an incremental patch? It should be just a one liner. I will squash it
> with your change. I can ping you on the other email as well.

I replied in the other thread. That one line is already in the final patch ;)

> I intend to use sparse-dev as the unstable sparse developer repo. It
> will always be based on sparse repo but the commit in sparse-dev can
> be rewinded. Patches will sit in the sparse-dev for about a week then
> move into sparse repo. The sparse repo is a stable repo, it will not
> rewind.
> 
> BTW, the recommended base to submit the sparse patches is the stable
> sparse repo unless you depend on some bleeding edge feature only on
> sparse-dev repo. Pull request please base on the sparse repo not the
> unstable sparse-dev repo.
Ack. At the moment, I am not planning to do more sparse development, this patch
will likely be a one shot. But I will keep this in mind if I either decide to do
another contribution.


Yours sincerely,
Vincent Mailhol