linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chandra Annamaneni <chandra627@gmail.com>
To: gregkh@linuxfoundation.org
Cc: gneukum1@gmail.com, dan.carpenter@oracle.com,
	michael.scheiderer@fau.de, fabian.krueger@fau.de,
	chandra627@gmail.com, simon@nikanor.nu,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (missing blank line)
Date: Wed, 16 Oct 2019 00:49:24 -0700	[thread overview]
Message-ID: <20191016074927.20056-1-chandra627@gmail.com> (raw)

Resolved: "CHECK: Please use a blank line after.." from checkpatch.pl

Signed-off-by: Chandra Annamaneni <chandra627@gmail.com>
---
Previous versions of these patches were not split into different 
patches, did not have different patch numbers and did not have the
keyword staging.
 drivers/staging/kpc2000/kpc2000_spi.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/kpc2000/kpc2000_spi.c b/drivers/staging/kpc2000/kpc2000_spi.c
index 6ba94b0131da..5712a88c8788 100644
--- a/drivers/staging/kpc2000/kpc2000_spi.c
+++ b/drivers/staging/kpc2000/kpc2000_spi.c
@@ -50,6 +50,7 @@ static struct flash_platform_data p2kr0_spi0_pdata = {
 	.nr_parts =	ARRAY_SIZE(p2kr0_spi0_parts),
 	.parts =	p2kr0_spi0_parts,
 };
+
 static struct flash_platform_data p2kr0_spi1_pdata = {
 	.name =		"SPI1",
 	.nr_parts =	ARRAY_SIZE(p2kr0_spi1_parts),
-- 
2.20.1


             reply	other threads:[~2019-10-16  7:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  7:49 Chandra Annamaneni [this message]
2019-10-16  7:49 ` [PATCH 2/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (alignment) Chandra Annamaneni
2019-10-16 14:54   ` Dan Carpenter
2019-10-16  7:49 ` [PATCH 3/4] " Chandra Annamaneni
2019-10-16  7:49 ` [PATCH 4/4] staging: KPC2000: kpc2000_spi.c: Fix style issues (Unnecessary parenthesis) 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=20191016074927.20056-1-chandra627@gmail.com \
    --to=chandra627@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabian.krueger@fau.de \
    --cc=gneukum1@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).