From: "Ricardo B. Marlière via ltp" <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>, <ltp@lists.linux.it>
Cc: ltp <ltp-bounces+ricardo=marliere.net@lists.linux.it>
Subject: Re: [LTP] [PATCH 0/4] checkpatch: Add .checkpatch.conf
Date: Fri, 24 Apr 2026 08:57:33 -0300 [thread overview]
Message-ID: <DI1D7VK7616J.RBUN51CEDKHM@suse.com> (raw)
In-Reply-To: <20260424093919.500059-1-pvorel@suse.cz>
On Fri Apr 24, 2026 at 6:39 AM -03, Petr Vorel wrote:
> Enhancement to reduce duplicity + add more checks.
>
> Petr Vorel (4):
> Update spellings to next-20260423
> checkpatch: Update to use new features
> Add .checkpatch.conf for checkpatch.pl
> checkpatch: Enable more checks, disable ENOSYS
>
> .b4-config | 5 +-
> .checkpatch.conf | 19 +++
> .gitignore | 3 +
> include/mk/env_post.mk | 2 +-
> scripts/checkpatch.pl | 133 ++++++++++++++---
> scripts/spelling.txt | 331 +++++++++++++++++++++--------------------
> 6 files changed, 303 insertions(+), 190 deletions(-)
> create mode 100644 .checkpatch.conf
Nice improvement, thanks!
Reviewed-by: Ricardo B. Marlière <rbm@suse.com>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-24 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:39 [LTP] [PATCH 0/4] checkpatch: Add .checkpatch.conf Petr Vorel
2026-04-24 9:39 ` [LTP] [PATCH 1/4] Update spellings to next-20260423 Petr Vorel
2026-04-24 10:25 ` [LTP] " linuxtestproject.agent
2026-04-24 11:36 ` Petr Vorel
2026-04-28 7:22 ` Andrea Cervesato via ltp
2026-04-24 9:39 ` [LTP] [PATCH 2/4] checkpatch: Update to use new features Petr Vorel
2026-04-24 9:39 ` [LTP] [PATCH 3/4] Add .checkpatch.conf for checkpatch.pl Petr Vorel
2026-04-24 9:39 ` [LTP] [PATCH 4/4] checkpatch: Enable more checks, disable ENOSYS Petr Vorel
2026-04-24 11:57 ` Ricardo B. Marlière via ltp [this message]
2026-04-29 8:06 ` [LTP] [PATCH 0/4] checkpatch: Add .checkpatch.conf 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=DI1D7VK7616J.RBUN51CEDKHM@suse.com \
--to=ltp@lists.linux.it \
--cc=ltp-bounces+ricardo=marliere.net@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rbm@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.