mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chandra Annamaneni <chandra627@gmail.com>
Cc: devel@driverdev.osuosl.org, gneukum1@gmail.com,
	michael.scheiderer@fau.de, fabian.krueger@fau.de,
	linux-kernel@vger.kernel.org, simon@nikanor.nu,
	dan.carpenter@oracle.com
Subject: Re: [PATCH 2/5] KPC2000: kpc2000_spi.c: Fix style issues (missing blank line)
Date: Fri, 11 Oct 2019 08:33:21 +0200	[thread overview]
Message-ID: <20191011063321.GB986093@kroah.com> (raw)
In-Reply-To: <20191011055155.4985-2-chandra627@gmail.com>

On Thu, Oct 10, 2019 at 10:51:52PM -0700, Chandra Annamaneni wrote:
> Resolved: "CHECK: Please use a blank line after.." from checkpatch.pl
> 
> Signed-off-by: Chandra Annamaneni <chandra627@gmail.com>

Please fix the subject lines for all of these patches and resend.

Also, this is a second set of patches, right?  What changed from the
first ones?  You should properly version your patches and explain under
the --- line what changed as the documentation states to.

Please do that for when you resend these.

thanks,

greg k-h

  reply	other threads:[~2019-10-11  6:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  5:51 [PATCH 1/5] KPC2000: kpc2000_spi.c: Fix style issues (line length) Chandra Annamaneni
2019-10-11  5:51 ` [PATCH 2/5] KPC2000: kpc2000_spi.c: Fix style issues (missing blank line) Chandra Annamaneni
2019-10-11  6:33   ` Greg KH [this message]
     [not found]     ` <CAEge-i7Va8NrVGYzssFqvuGEwV=xPu9VL5_ZewXn2985QbEmcw@mail.gmail.com>
2019-10-11  9:11       ` Greg KH
2019-10-11  5:51 ` [PATCH 3/5] KPC2000: kpc2000_spi.c: Fix style issues (misaligned brace) Chandra Annamaneni
2019-10-11  5:51 ` [PATCH 4/5] KPC2000: kpc2000_spi.c: Fix style issues (alignment) Chandra Annamaneni
2019-10-11  5:51 ` [PATCH 5/5] KPC2000: kpc2000_spi.c: Fix style issues (Unnecessary parenthesis) Chandra Annamaneni
2019-10-11  6:32 ` [PATCH 1/5] KPC2000: kpc2000_spi.c: Fix style issues (line length) Greg KH
2019-10-16  7:42   ` <Chandra Annamaneni>

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=20191011063321.GB986093@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chandra627@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabian.krueger@fau.de \
    --cc=gneukum1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.scheiderer@fau.de \
    --cc=simon@nikanor.nu \
    /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®