All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
Cc: joe@perches.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] staging: rtl8192e: fix coding style issues (merge broken strings)
Date: Mon, 16 Mar 2015 16:02:40 +0100	[thread overview]
Message-ID: <20150316150240.GA16015@kroah.com> (raw)
In-Reply-To: <1426451987-24519-2-git-send-email-mateusz.kulikowski@gmail.com>

On Sun, Mar 15, 2015 at 09:39:43PM +0100, Mateusz Kulikowski wrote:
> Fix checkpatch.pl warnings:
> - 'WARNING: quoted string split across lines'
> - 'WARNING: break quoted strings at a space character'
> 
> Signed-off-by: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
> ---

This patch fails to apply to my staging-testing branch of staging-next
:(

Can you please refresh this series against that branch and resend?

thanks,

greg k-h

  reply	other threads:[~2015-03-16 15:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 20:39 [PATCH v4 0/5] staging: rtl8192e: fix coding style issues Mateusz Kulikowski
2015-03-15 20:39 ` [PATCH v4 1/5] staging: rtl8192e: fix coding style issues (merge broken strings) Mateusz Kulikowski
2015-03-16 15:02   ` Greg KH [this message]
2015-03-15 20:39 ` [PATCH v4 2/5] staging: rtl8192e: fix coding style issues (spaces before semicolon) Mateusz Kulikowski
2015-03-15 20:39 ` [PATCH v4 3/5] staging: rtl8192e: fix coding style errors (macros in parentheses) Mateusz Kulikowski
2015-03-16  4:51   ` Joe Perches
2015-03-16 22:58     ` Mateusz Kulikowski
2015-03-15 20:39 ` [PATCH v4 4/5] staging: rtl8192e: rtllib_wx: remove duplicate messages Mateusz Kulikowski
2015-03-15 20:39 ` [PATCH v4 5/5] staging: rtl8192e: fix coding style warnings (printk -> netdev_*) Mateusz Kulikowski

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=20150316150240.GA16015@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mateusz.kulikowski@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 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.