From: Joe Perches <joe@perches.com>
To: Michal Kalderon <michal.kalderon@marvell.com>,
leon@kernel.org, apw@canonical.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: add test for empty line after Fixes statement
Date: Mon, 20 May 2019 05:56:36 -0700 [thread overview]
Message-ID: <ed26df86d7d0e12263404842895460b1611def61.camel@perches.com> (raw)
In-Reply-To: <20190520124238.10298-1-michal.kalderon@marvell.com>
On Mon, 2019-05-20 at 15:42 +0300, Michal Kalderon wrote:
> Check that there is no empty line after a fixes statement
why?
next prev parent reply other threads:[~2019-05-20 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 12:42 [PATCH] checkpatch: add test for empty line after Fixes statement Michal Kalderon
2019-05-20 12:56 ` Joe Perches [this message]
2019-05-20 13:16 ` Leon Romanovsky
2019-05-20 13:16 ` [EXT] " Michal Kalderon
2019-05-20 13:34 ` Joe Perches
2019-05-20 13:52 ` Leon Romanovsky
2019-05-21 0:07 ` Joe Perches
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=ed26df86d7d0e12263404842895460b1611def61.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.kalderon@marvell.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;
as well as URLs for NNTP newsgroup(s).