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 1/5] KPC2000: kpc2000_spi.c: Fix style issues (line length)
Date: Fri, 11 Oct 2019 08:32:19 +0200 [thread overview]
Message-ID: <20191011063219.GA986093@kroah.com> (raw)
In-Reply-To: <20191011055155.4985-1-chandra627@gmail.com>
On Thu, Oct 10, 2019 at 10:51:51PM -0700, Chandra Annamaneni wrote:
> Resoved: "WARNING: line over 80 characters" from checkpatch.pl
Please put "staging:" in your subject line, makes it easier to sort and
handle. It should look something like:
staging: kpc2000_spi: fix line length issues
Looks a lot cleaner, right?
>
> Signed-off-by: Chandra Annamaneni <chandra627@gmail.com>
> ---
> drivers/staging/kpc2000/kpc2000_spi.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/kpc2000/kpc2000_spi.c b/drivers/staging/kpc2000/kpc2000_spi.c
> index 3be33c450cab..81d79b116ce0 100644
> --- a/drivers/staging/kpc2000/kpc2000_spi.c
> +++ b/drivers/staging/kpc2000/kpc2000_spi.c
> @@ -30,19 +30,19 @@
> #include "kpc.h"
>
> static struct mtd_partition p2kr0_spi0_parts[] = {
> - { .name = "SLOT_0", .size = 7798784, .offset = 0, },
> - { .name = "SLOT_1", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> - { .name = "SLOT_2", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> - { .name = "SLOT_3", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> - { .name = "CS0_EXTRA", .size = MTDPART_SIZ_FULL, .offset = MTDPART_OFS_NXTBLK},
> + { .name = "SLOT_0", .size = 7798784, .offset = 0, },
> + { .name = "SLOT_1", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> + { .name = "SLOT_2", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> + { .name = "SLOT_3", .size = 7798784, .offset = MTDPART_OFS_NXTBLK},
> + { .name = "CS0_EXTRA", .size = MTDPART_SIZ_FULL, .offset = MTDPART_OFS_NXTBLK},
Why did you pick 2 spaces here as a random choice of padding? That's
very odd, please don't.
Either leave this alone (as it lines everything up nicely), or only use
one space. I would suggest just leaving it alone.
thanks,
greg k-h
next prev parent reply other threads:[~2019-10-11 6:33 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
[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 ` Greg KH [this message]
2019-10-16 7:42 ` [PATCH 1/5] KPC2000: kpc2000_spi.c: Fix style issues (line length) <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=20191011063219.GA986093@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