linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Juston Li <juston.h.li@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
	linux-fbdev@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v4 01/19] staging: sm750fb: use tabs for indentation
Date: Wed, 15 Jul 2015 01:30:51 +0000	[thread overview]
Message-ID: <20150715013051.GA15700@kroah.com> (raw)
In-Reply-To: <1435600536-13135-1-git-send-email-juston.h.li@gmail.com>

On Mon, Jun 29, 2015 at 10:55:18AM -0700, Juston Li wrote:
> Replace spaces with tabs for indentation to fix the checkpatch.pl error
> ERROR: code indent should use tabs where possible
> WARNING: please, no spaces at the start of a line

Due to other patches that came in before yours, that are now in my tree,
this patch doesn't apply.  Can you please rebase it against my
staging-testing branch of staging.git and resend?

thanks,

greg k-h

  reply	other threads:[~2015-07-15  1:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 17:12 [PATCH v4 00/19] staging: sm750fb: checkpatch.pl fixes Juston Li
2015-06-29 17:55 ` [PATCH v4 01/19] staging: sm750fb: use tabs for indentation Juston Li
2015-07-15  1:30   ` Greg KH [this message]
2015-06-29 17:55 ` [PATCH v4 02/19] staging: sm750fb: remove spacing after open parenthesis Juston Li
2015-06-29 17:55 ` [PATCH v4 03/19] staging: sm750fb: remove space before close parenthesis Juston Li
2015-06-29 17:55 ` [PATCH v4 04/19] staging: sm750fb: add space before open parenthesis Juston Li
2015-06-29 17:55 ` [PATCH v4 05/19] staging: sm750fb: remove space between function name and parenthesis Juston Li
2015-06-29 17:55 ` [PATCH v4 06/19] staging: sm750fb: add space before open brace Juston Li
2015-06-29 17:55 ` [PATCH v4 07/19] staging: sm750fb: add space after close brace Juston Li
2015-06-29 17:55 ` [PATCH v4 08/19] staging: sm750fb: add space after enum definition Juston Li
2015-06-29 17:55 ` [PATCH v4 09/19] staging: sm750fb: add space after struct definition Juston Li
2015-06-29 17:55 ` [PATCH v4 10/19] staging: sm750fb: add space after return type Juston Li
2015-06-29 17:55 ` [PATCH v4 11/19] staging: sm750fb: consistent spacing around operators Juston Li
2015-06-29 17:55 ` [PATCH v4 12/19] staging: sm750fb: add spaces " Juston Li
2015-06-29 17:55 ` [PATCH v4 13/19] staging: sm750fb: add space after semicolon Juston Li
2015-06-29 17:55 ` [PATCH v4 14/19] staging: sm750fb: remove trailing whitespace Juston Li
2015-06-29 17:55 ` [PATCH v4 15/19] staging: sm750fb: remove unnecessary whitespace Juston Li
2015-06-29 17:55 ` [PATCH v4 16/19] staging: sm750fb: fix brace placement Juston Li
2015-06-29 17:55 ` [PATCH v4 17/19] staging: sm750fb: move while to follow do close brace Juston Li
2015-06-29 17:55 ` [PATCH v4 18/19] staging: sm750fb: remove unnecessary braces Juston Li
2015-06-29 17:55 ` [PATCH v4 19/19] staging: sm750fb: add missing blank line after declarations Juston Li

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=20150715013051.GA15700@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=juston.h.li@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=teddy.wang@siliconmotion.com \
    /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).