From: Florian Westphal <fw@strlen.de>
To: chenguohua@jari.cn
Cc: pablo@netfilter.org, kadlec@netfilter.org, fw@strlen.de,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: Clean up errors in nf_conntrack_h323_asn1.h
Date: Sun, 8 Oct 2023 14:29:35 +0200 [thread overview]
Message-ID: <20231008122935.GB29696@breakpoint.cc> (raw)
In-Reply-To: <33d535ba.863.18ad54575ed.Coremail.chenguohua@jari.cn>
chenguohua@jari.cn <chenguohua@jari.cn> wrote:
> Fix the following errors reported by checkpatch:
>
> ERROR: "foo * bar" should be "foo *bar"
Running "checkpatch -f" for all nf related files results
in a myriad of "warnings". I don't think there is a good
reason to "fix" them.
checkpatch is good for new patch submissions, but I
do not think its worth it to adjust all the existing files.
Sorry.
prev parent reply other threads:[~2023-10-08 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 6:13 [PATCH] netfilter: Clean up errors in nf_conntrack_h323_asn1.h chenguohua
2023-10-08 12:29 ` Florian Westphal [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=20231008122935.GB29696@breakpoint.cc \
--to=fw@strlen.de \
--cc=chenguohua@jari.cn \
--cc=coreteam@netfilter.org \
--cc=kadlec@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 NNTP newsgroup(s).