From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Justin Stitt <justinstitt@google.com>
Cc: "Kernel.org Tools" <tools@linux.kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH b4] b4: add checkpatch via prep --check
Date: Tue, 8 Aug 2023 12:18:38 -0400 [thread overview]
Message-ID: <20230808-equipment-aspire-c4bd2d@meerkat> (raw)
In-Reply-To: <20230803-add-checkpatch-v1-1-2952aee9e2a8@google.com>
On Thu, Aug 03, 2023 at 10:45:53PM +0000, Justin Stitt wrote:
> This patch adds support for the following incantation:
>
> `$ b4 prep --check`
Justin:
I see your patch, but I want to step back a bit and have a broader discussion
about various pre-send integration checks, especially when it comes to how we
report errors and warnings to the developer running the check.
I will send a follow-up topic to the tools and users lists. For now, let's sit
on this and adjust based on the feedback I receive.
-K
prev parent reply other threads:[~2023-08-08 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 22:45 [PATCH b4] b4: add checkpatch via prep --check Justin Stitt
2023-08-08 16:18 ` Konstantin Ryabitsev [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=20230808-equipment-aspire-c4bd2d@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=justinstitt@google.com \
--cc=ndesaulniers@google.com \
--cc=tools@linux.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).