public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Christoph Schlameuss <schlameuss@linux.ibm.com>, kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Andrew Jones <andrew.jones@linux.dev>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [kvm-unit-tests PATCH 0/3] scripts: Configure and update tools to allow basic b4 usage
Date: Fri, 24 Apr 2026 09:19:00 +0200	[thread overview]
Message-ID: <16bf7ab2-c4ad-4982-9170-cd06015c39f9@redhat.com> (raw)
In-Reply-To: <20260423-b4-cmdline-v1-0-f72ad0020d42@linux.ibm.com>

On 23/04/2026 16.16, Christoph Schlameuss wrote:
> Provide some basic configuration for checkpatch.pl so that use on the
> command line is less confusing and actually useful.
> Checking new patches with i.e. 'b4 prep --check' will now not just give you
> dummy errors.
> 
> Modify get_maintainer.pl to work when called from 'b4 prep --auto-to-cc'.
> 
> ---
> The second patch also copies the current codespell config from the kernel.
> I think this would be nice to have but I would also understand if nobody
> wants to add that dead weight here. In that case I would also agree drop
> that second patch.

IMHO the dictionary that comes along with the codespell utility should 
already be good enough to cover most of these typos, so I'm inclined to 
rather say "no" to the second patch. Instead, maybe you could introduce a 
k-u-t specific spelling.txt to get rid of the warning message, with some few 
entries like:

kmv||kvm
RDSMR||RDMSR
WRSMR||WRMSR

?

(the latter two entries were fixed by commit 784dd85d25d484)

WDYT?

  Thomas


  parent reply	other threads:[~2026-04-24  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 14:16 [kvm-unit-tests PATCH 0/3] scripts: Configure and update tools to allow basic b4 usage Christoph Schlameuss
2026-04-23 14:16 ` [kvm-unit-tests PATCH 1/3] scripts/checkpatch.pl: Add empty codespell and const_structs configs Christoph Schlameuss
2026-04-24  7:00   ` Thomas Huth
2026-04-24  7:36     ` Christoph Schlameuss
2026-04-23 14:16 ` [kvm-unit-tests PATCH 2/3] scripts/checkpatch.pl: Copy kernel codespell file Christoph Schlameuss
2026-04-23 14:16 ` [kvm-unit-tests PATCH 3/3] scripts/get_maintainer.pl: Ignore --nogit-chief-penguins option Christoph Schlameuss
2026-04-24  7:31   ` Thomas Huth
2026-04-24  7:41     ` Christoph Schlameuss
2026-04-24  7:19 ` Thomas Huth [this message]
2026-04-24  7:42   ` [kvm-unit-tests PATCH 0/3] scripts: Configure and update tools to allow basic b4 usage Christoph Schlameuss

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=16bf7ab2-c4ad-4982-9170-cd06015c39f9@redhat.com \
    --to=thuth@redhat.com \
    --cc=andrew.jones@linux.dev \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=schlameuss@linux.ibm.com \
    /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