From: Joe Perches <joe@perches.com>
To: Prakruthi Deepak Heragu <pheragu@codeaurora.org>, apw@canonical.com
Cc: linux-kernel@vger.kernel.org, tsoni@codeaurora.org,
ckadabi@codeaurora.org, bryanh@codeaurora.org
Subject: Re: [PATCH] checkpatch: Handle long multi-line macros better
Date: Tue, 10 Jul 2018 10:46:16 -0700 [thread overview]
Message-ID: <5f85df9e26a3ca19e5a6b65a0d8df194581ab29c.camel@perches.com> (raw)
In-Reply-To: <1531244524-16003-1-git-send-email-pheragu@codeaurora.org>
On Tue, 2018-07-10 at 10:42 -0700, Prakruthi Deepak Heragu wrote:
> Currently, the checkpatch throws an error on long macro expressions which
> is more than one line i.e the opening and the closing bracket pair not
> being on the same line. This patch gives the dangling backslash the
> benefit of doubt and allows it to consider the closing paranthesis on the
> next line as part of the macro expression and doesn't throw an error.
Example please.
prev parent reply other threads:[~2018-07-10 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 17:42 Prakruthi Deepak Heragu
2018-07-10 17:46 ` 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=5f85df9e26a3ca19e5a6b65a0d8df194581ab29c.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pheragu@codeaurora.org \
--cc=tsoni@codeaurora.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®