mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Chuang <founder@logarcheon.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Howells <dhowells@redhat.com>,
	keyrings@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] lib/asn1_decoder: add KUnit test suite
Date: Tue, 17 Nov 2026 22:44:17 +0000	[thread overview]
Message-ID: <20261117224411.7043-1-founder@logarcheon.com> (raw)
In-Reply-To: <avvI1PuQUtBlfZWP@kernel.org>

On Tue, Nov 17, 2026 at 05:24:04AM +0200, Jarkko Sakkinen wrote:
> Within past 17 years the total number of commits is 22. This includes
> all the possible. Of these total six carry a Fixes tag.
>
> That makes about 0.35 bug fixes annually. How do you explain this

That is a fair measure.  With a change to the decoder every nine
months or so, a regression suite has little to catch, and its upkeep
would fall on you and the other maintainers.  I'm withdrawing this
RFC.

> Your previous kunit supports this point of view given that it is
> a possible "LLM remix" of a patch (kunit for assoc_array) that I
> sent a month ago but we discarded the idea in favor of a better
> solution.

I had not seen your October patch when I sent mine.  I should have
searched lore first, and I will before sending anything further.

> Stop doing this.

Understood: no more test-only patches for this code from me.  Sorry
as well for the badly formatted reply earlier.

Thanks,
William


      reply	other threads:[~2026-11-17 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  0:17 William Chuang
2026-11-17  1:32 ` Jarkko Sakkinen
2026-11-17  2:39   ` William Chuang, Founder – Logarcheon
2026-11-17  3:09     ` Jarkko Sakkinen
2026-11-17  3:24       ` Jarkko Sakkinen
2026-11-17 22:44         ` William Chuang [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=20261117224411.7043-1-founder@logarcheon.com \
    --to=founder@logarcheon.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®