From: Joe Perches <joe@perches.com>
To: Jerome Forissier <jerome.forissier@linaro.org>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: don't match against empty $const_structs
Date: Thu, 20 Oct 2016 01:25:39 -0700 [thread overview]
Message-ID: <1476951939.21931.3.camel@perches.com> (raw)
In-Reply-To: <bc553cb0-5bd5-ea08-bfc4-c75d2ce0ddf3@linaro.org>
On Thu, 2016-10-20 at 10:18 +0200, Jerome Forissier wrote:
> On 10/20/2016 10:16 AM, Joe Perches wrote
> . Why should $const_structs ever be empty?
> When running out-of-tree, i.e., using checkpatch.pl on non-kernel sources.
Oh, alright.
prev parent reply other threads:[~2016-10-20 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 8:12 Jerome Forissier
2016-10-20 8:16 ` Joe Perches
2016-10-20 8:18 ` Jerome Forissier
2016-10-20 8:25 ` Joe Perches [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=1476951939.21931.3.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=jerome.forissier@linaro.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®