All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Leo Kim <leo.kim@atmel.com>
Cc: devel@driverdev.osuosl.org, Chris Park <chris.park@atmel.com>,
	austin.shin@atmel.com, linux-wireless@vger.kernel.org,
	Nicolas.FERRE@atmel.com, tony.cho@atmel.com,
	adham.abozaeid@atmel.com
Subject: Re: [PATCH 1/6] staging: wilc1000: fix warnings for line over 80 characters
Date: Wed, 3 Feb 2016 15:32:43 -0800	[thread overview]
Message-ID: <20160203233243.GA14810@kroah.com> (raw)
In-Reply-To: <1454050298-25815-1-git-send-email-leo.kim@atmel.com>

On Fri, Jan 29, 2016 at 03:51:33PM +0900, Leo Kim wrote:
> From: Chris Park <chris.park@atmel.com>
> 
> This patch fixes warnings reported by checkpatch.pl
> for line over 80 characters
> 
> Signed-off-by: Chris Park <chris.park@atmel.com>
> Signed-off-by: Leo Kim <leo.kim@atmel.com>

This series didn't apply either, please fix up and resend.

thanks,

greg k-h

      parent reply	other threads:[~2016-02-03 23:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  6:51 [PATCH 1/6] staging: wilc1000: fix warnings for line over 80 characters Leo Kim
2016-01-29  6:51 ` [PATCH 2/6] staging: wilc1000: remove useless log message Leo Kim
2016-01-29  6:51 ` [PATCH 3/6] staging: wilc1000: remove useless function Leo Kim
2016-01-29  6:51 ` [PATCH 4/6] staging: wilc1000: remove unnecessary braces Leo Kim
2016-01-29  6:51 ` [PATCH 5/6] staging: wilc1000: remove warnings missing a blank line after declarations Leo Kim
2016-01-29  6:51 ` [PATCH 6/6] staging: wilc1000: Optimize code of wilc_get_chipid function Leo Kim
2016-02-03 23:32 ` 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=20160203233243.GA14810@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Nicolas.FERRE@atmel.com \
    --cc=adham.abozaeid@atmel.com \
    --cc=austin.shin@atmel.com \
    --cc=chris.park@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=leo.kim@atmel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tony.cho@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.