From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: john.hubbard@gmail.com
Cc: "Dan Carpenter" <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, "Vandana BN" <bnvandana@gmail.com>,
"Geordan Neukum" <gneukum1@gmail.com>,
"Bharath Vedartham" <linux.bhar@gmail.com>,
"John Hubbard" <jhubbard@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
"Simon Sandström" <simon@nikanor.nu>
Subject: Re: [PATCH] staging: kpc2000: whitespace and line length cleanup
Date: Tue, 16 Jul 2019 17:36:53 +0900 [thread overview]
Message-ID: <20190716083653.GB26457@kroah.com> (raw)
In-Reply-To: <20190715212123.432-2-jhubbard@nvidia.com>
On Mon, Jul 15, 2019 at 02:21:23PM -0700, john.hubbard@gmail.com wrote:
> From: John Hubbard <jhubbard@nvidia.com>
>
> This commit was created by running indent(1):
> `indent -linux`
>
> ...and then applying some manual corrections and
> cleanup afterward, to keep it sane. No functional changes
> were made.
>
> In addition to whitespace changes, some strings were split,
> but not strings that were likely to be a grep problem
> (in other words, if a user is likely to grep for a string
> within the driver, that should still work in most cases).
>
> A few "void * foo" cases were fixed to be "void *foo".
>
> That was enough to make checkpatch.pl run without errors,
> although note that there are lots of serious warnings
> remaining--but those require functional, not just whitespace
> changes. So those are left for a separate patch.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Simon Sandström <simon@nikanor.nu>
> Cc: Geordan Neukum <gneukum1@gmail.com>
> Cc: Jeremy Sowden <jeremy@azazel.net>
> Cc: Dan Carpenter <dan.carpenter@oracle.com>
> Cc: Vandana BN <bnvandana@gmail.com>
> Cc: devel@driverdev.osuosl.org
> Cc: Bharath Vedartham <linux.bhar@gmail.com>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
> drivers/staging/kpc2000/kpc2000_i2c.c | 189 +++++++++++------
> drivers/staging/kpc2000/kpc2000_spi.c | 116 +++++-----
> drivers/staging/kpc2000/kpc_dma/dma.c | 109 ++++++----
> drivers/staging/kpc2000/kpc_dma/fileops.c | 199 +++++++++++-------
> .../staging/kpc2000/kpc_dma/kpc_dma_driver.c | 113 +++++-----
> .../staging/kpc2000/kpc_dma/kpc_dma_driver.h | 156 +++++++-------
> 6 files changed, 509 insertions(+), 373 deletions(-)
THat's way too many different types of changes to do all at once, and
some of these are making the code look worse, not better.
There's a reason we don't run lindent :)
If you want to do one-type-of-fix-per-patch, I'll gladly take these,
otherwise, I recommend leaving this for those people learning how to do
development to do.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-16 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 21:21 [PATCH 0/1] staging: kpc2000: whitespace and line length cleanup john.hubbard
2019-07-15 21:21 ` [PATCH] " john.hubbard
2019-07-15 22:21 ` Joe Perches
2019-07-15 22:26 ` John Hubbard
2019-07-16 8:36 ` Greg Kroah-Hartman [this message]
2019-07-16 18:02 ` John Hubbard
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=20190716083653.GB26457@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bnvandana@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gneukum1@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@gmail.com \
--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