From: Gal Pressman <gal@nvidia.com>
To: Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: .clang-format vs. checkpatch: Lines should not end with a '('
Date: Thu, 19 Jan 2023 16:16:33 +0200 [thread overview]
Message-ID: <88d82daa-811a-0cb7-8b83-7eb828b4fae8@nvidia.com> (raw)
Hey,
I use clang-format to automatically format my patches, but checkpatch
likes to complain about:
CHECK: Lines should not end with a '('
I thought maybe adding a 'AllowAllArgumentsOnNextLine: false' would make
it happy but that didn't really seem to work.
Anyone else a bit annoyed by this? Maybe there's another solution I'm
failing to see?
Thanks
next reply other threads:[~2023-01-19 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 14:16 Gal Pressman [this message]
2023-01-19 16:57 ` .clang-format vs. checkpatch: Lines should not end with a '(' David Laight
2023-01-22 7:16 ` Gal Pressman
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=88d82daa-811a-0cb7-8b83-7eb828b4fae8@nvidia.com \
--to=gal@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=trix@redhat.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