mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CaoRuichuang <create0818@163.com>
To: apw@canonical.com, joe@perches.com
Cc: dwaipayanray1@gmail.com, lukas.bulwahn@gmail.com,
	linux-kernel@vger.kernel.org, CaoRuichuang <create0818@163.com>
Subject: [PATCH v2 0/2] scripts: support sparse checkouts in checkpatch tools
Date: Mon,  6 Apr 2026 03:15:53 +0800	[thread overview]
Message-ID: <20260405191555.80315-1-create0818@163.com> (raw)
In-Reply-To: <20260405185504.76040-1-create0818@163.com>

checkpatch.pl and get_maintainer.pl currently reject sparse checkouts because their top_of_kernel_tree() checks require top-level directories that may not be present in a sparse working tree.

This series relaxes that check to match the files the scripts actually need and adds a regression test to keep that behavior from regressing.

Changes in v2:
  - add a regression test for sparse checkout handling in checkpatch.pl and
    get_maintainer.pl


CaoRuichuang (2):
  scripts: allow checkpatch and get_maintainer in sparse checkouts
  scripts: add sparse checkout regression test for checkpatch tools

 scripts/checkpatch-sparse-checkout-test.sh | 48 ++++++++++++++++++++++
 scripts/checkpatch.pl                      |  4 +-
 scripts/get_maintainer.pl                  |  9 +---
 3 files changed, 51 insertions(+), 10 deletions(-)
 create mode 100755 scripts/checkpatch-sparse-checkout-test.sh

-- 
2.39.5 (Apple Git-154)


  parent reply	other threads:[~2026-04-05 19:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 18:55 [PATCH] scripts: allow checkpatch and get_maintainer in sparse checkouts CaoRuichuang
2026-04-05 19:12 ` Joe Perches
2026-04-05 19:15 ` CaoRuichuang [this message]
2026-04-05 19:15   ` [PATCH v2 1/2] " CaoRuichuang
2026-04-05 19:26     ` Joe Perches
2026-04-05 19:39       ` CaoRuichuang
2026-04-05 19:15   ` [PATCH v2 2/2] scripts: add sparse checkout regression test for checkpatch tools CaoRuichuang

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=20260405191555.80315-1-create0818@163.com \
    --to=create0818@163.com \
    --cc=apw@canonical.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.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

all inboxes | Powered by JetHome®