linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Konopko <kris@konagma.com>
Cc: navin.patidar@gmail.com, Larry Finger <Larry.Finger@lwfinger.net>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] rtl8188eu:  Remove leading spaces in rtw_led.c
Date: Wed, 26 Nov 2014 15:27:19 -0800	[thread overview]
Message-ID: <20141126232719.GA12287@kroah.com> (raw)
In-Reply-To: <1415316268-10278-3-git-send-email-kris@konagma.com>

On Fri, Nov 07, 2014 at 12:24:28AM +0100, Krzysztof Konopko wrote:
> According to Linux coding convention leading spaces are not allowed.  This
> patch removes leading spaces in rtw_led.c
> 
> Signed-off-by: Krzysztof Konopko <kris@konagma.com>
> ---
>  drivers/staging/rtl8188eu/core/rtw_led.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/rtl8188eu/core/rtw_led.c b/drivers/staging/rtl8188eu/core/rtw_led.c
> index 1b8264b..5d7e8ec 100644
> --- a/drivers/staging/rtl8188eu/core/rtw_led.c
> +++ b/drivers/staging/rtl8188eu/core/rtw_led.c
> @@ -40,6 +40,7 @@ void BlinkTimerCallback(void *data)
>  void BlinkWorkItemCallback(struct work_struct *work)
>  {
>  	struct LED_871x *pLed = container_of(work, struct LED_871x, BlinkWorkItem);
> +
>  	BlinkHandler(pLed);
>  }

This is not a "fix leading space" change :(

      reply	other threads:[~2014-11-27  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 23:24 [PATCH 1/3] rtl8188eu: Fix FSF_MAILING_ADDRESS in rtw_led.* Krzysztof Konopko
2014-11-06 23:24 ` [PATCH 2/3] rtl8188eu: Fix a typo " Krzysztof Konopko
2014-11-06 23:24   ` [PATCH 3/3] rtl8188eu: Remove leading spaces in rtw_led.c Krzysztof Konopko
2014-11-26 23:27     ` Greg Kroah-Hartman [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=20141126232719.GA12287@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=kris@konagma.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=navin.patidar@gmail.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).