From: Andrew Morton <akpm@linux-foundation.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Cryolitia PukNgae <cryolitia@uniontech.com>
Subject: Re: [PATCH v5 0/5] checkpatch: userspace improvements
Date: Tue, 1 Sep 2026 10:44:04 -0700 [thread overview]
Message-ID: <20260901104404.55d26e883e9917548025d3a9@linux-foundation.org> (raw)
In-Reply-To: <20260901105642.851234-1-pvorel@suse.cz>
On Tue, 1 Sep 2026 12:56:37 +0200 Petr Vorel <pvorel@suse.cz> wrote:
> Changes v4->v5 (all by sashiko):
> * Explicitly match the directory separator in new entries for
> is_userspace()
> * Allow --no-userspace to override setup in the config (using undef
> instead of 0, separate checks in is_userspace())
> * 2 new commits:
> - checkpatch: Factor out the check for UAPI files
> - checkpatch: Skip kernel specific checks for userspace
Please prepare a proper [0/N] overview for the series.
Sashiko still has much to say:
https://lore.kernel.org/lkml/20260810164552.1049483-1-pvorel@suse.cz/
In [4/5] changelog. What does "DRY" mean?
next prev parent reply other threads:[~2026-09-01 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 10:56 Petr Vorel
2026-09-01 10:56 ` [PATCH v5 1/5] checkpatch: Add more userspace directories to is_userspace() Petr Vorel
2026-09-01 10:56 ` [PATCH v5 2/5] checkpatch: Ignore <inttypes.h> format macros for userspace tools Petr Vorel
2026-09-01 10:56 ` [PATCH v5 3/5] checkpatch: Add --userspace to force userspace rules Petr Vorel
2026-09-01 10:56 ` [PATCH v5 4/5] checkpatch: Factor out the check for UAPI files Petr Vorel
2026-09-02 6:09 ` Petr Vorel
2026-09-01 10:56 ` [PATCH v5 5/5] checkpatch: Skip kernel specific checks for userspace Petr Vorel
2026-09-02 6:18 ` Petr Vorel
2026-09-01 17:44 ` Andrew Morton [this message]
2026-09-02 6:04 ` [PATCH v5 0/5] checkpatch: userspace improvements Petr Vorel
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=20260901104404.55d26e883e9917548025d3a9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=cryolitia@uniontech.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pvorel@suse.cz \
/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®