linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michel von Czettritz <michel.von.czettritz@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 02/13] staging: sm750: add missing spaces after ','
Date: Thu, 26 Mar 2015 15:28:12 +0000	[thread overview]
Message-ID: <5514258C.6050604@gmail.com> (raw)
In-Reply-To: <20150322231131.GA17080@x230-arch.club.entropia.de>

On 03/26/2015 01:06 PM, Greg KH wrote:
> On Mon, Mar 23, 2015 at 12:11:31AM +0100, Michel von Czettritz wrote:
>> Fixes checkpatch.pl error:
>> "ERROR: space required after that ',' (ctx:VxV)"
>>
>> Signed-off-by: Michel von Czettritz <michel.von.czettritz@gmail.com>
>> ---
>>  drivers/staging/sm750fb/sm750.c | 264 ++++++++++++++++++++--------------------
>>  1 file changed, 132 insertions(+), 132 deletions(-)
> 
> As I didn't take your first patch, the rest of the patches in this
> series do not apply.
> 
> Please fix them up, rebase on my latest staging-testing branch of
> staging.git, and resend so that I can apply them.
> 
> thanks,
> 
> greg k-h

I am, as a newbie, a bit confused. 
Should i resend my fixes with RESEND or with a v2 flag?
As Sudip i applied Lorenzos conflicting patches on statging-testing and rebased my patches on them. 
Should i wait until Lorenzos patches are applied?

regards Michel

> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  parent reply	other threads:[~2015-03-26 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 23:11 [PATCH 02/13] staging: sm750: add missing spaces after ',' Michel von Czettritz
2015-03-26 12:06 ` Greg KH
2015-03-26 15:28 ` Michel von Czettritz [this message]
2015-03-26 15:50 ` Dan Carpenter

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=5514258C.6050604@gmail.com \
    --to=michel.von.czettritz@gmail.com \
    --cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).