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 v6 0/4] checkpatch: userspace improvements
Date: Sat, 5 Sep 2026 18:22:00 -0700 [thread overview]
Message-ID: <20260905182200.f5bc96a5336d47e05bba0b49@linux-foundation.org> (raw)
In-Reply-To: <20260904110230.1219037-1-pvorel@suse.cz>
On Fri, 4 Sep 2026 13:02:26 +0200 Petr Vorel <pvorel@suse.cz> wrote:
> Few improvements for user space code + --userspace option for projects
> which vendored checkpatch.pl.
>
> There could be probably more checks which are kernel space only.
Thanks. Let me put this into mm.git's mm-nonmm-unstable branch (and
hence into linux-next) for testing and additional review.
> Follow-up: 99b70ece33d8 ("checkpatch: suppress strscpy warnings for userspace tools")
Sorry, I'm not a fan of inventing new tags. This isn't a documented
tag and nobody has ever used it before. I altered these to
: This is a follow-up to 99b70ece33d8 ("checkpatch: suppress strscpy
: warnings for userspace tools").
prev parent reply other threads:[~2026-09-06 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:02 Petr Vorel
2026-09-04 11:02 ` [PATCH v6 1/4] checkpatch: Add more userspace directories to is_userspace() Petr Vorel
2026-09-04 11:02 ` [PATCH v6 2/4] checkpatch: Ignore <inttypes.h> format macros for userspace tools Petr Vorel
2026-09-04 11:02 ` [PATCH v6 3/4] checkpatch: Add --userspace to force userspace rules Petr Vorel
2026-09-04 11:02 ` [PATCH v6 4/4] checkpatch: Skip kernel specific checks for userspace Petr Vorel
2026-09-06 1:22 ` Andrew Morton [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=20260905182200.f5bc96a5336d47e05bba0b49@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®