From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Eastman <eastman.jason.linux@gmail.com>
Cc: hofrat@osadl.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: image: mdc800: fixed various style issues
Date: Tue, 28 Apr 2015 12:40:44 +0200 [thread overview]
Message-ID: <20150428104044.GA540@kroah.com> (raw)
In-Reply-To: <1429833541-21717-1-git-send-email-eastman.jason.linux@gmail.com>
On Thu, Apr 23, 2015 at 05:59:01PM -0600, Jason Eastman wrote:
> Fixed several style issues with: comments, function perenthesis,
> indentation, and conditional braces
>
> Signed-off-by: Jason Eastman <eastman.jason.linux@gmail.com>
> ---
> drivers/usb/image/mdc800.c | 769 +++++++++++++++++++-------------------------
> 1 file changed, 336 insertions(+), 433 deletions(-)
That's a lot to fix all at "once", please break this up in to different
patches, each one only doing one thing at a time.
thanks,
greg k-h
prev parent reply other threads:[~2015-04-28 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 23:59 [PATCH] usb: image: mdc800: fixed various style issues Jason Eastman
2015-04-24 9:55 ` Varka Bhadram
2015-04-28 10:40 ` Greg KH [this message]
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=20150428104044.GA540@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eastman.jason.linux@gmail.com \
--cc=hofrat@osadl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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