All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: forest@alittletooquiet.net, tvboxspy@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues
Date: Sun, 13 Jul 2014 19:36:47 +0000	[thread overview]
Message-ID: <20140713193647.GA31010@kroah.com> (raw)
In-Reply-To: <1405278681-3348-1-git-send-email-peter.senna@gmail.com>

On Sun, Jul 13, 2014 at 09:11:18PM +0200, Peter Senna Tschudin wrote:
> This patch cleanup coding style issues reported by checkpatch.
> 
> Tested by compilation only.
> 
> Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
> ---
> Cahnges from V1:
>  - Sent all patches in a series

Why did you forget the other thing that I asked you to change?

I can't take these as-is, sorry, please go back and re-read what I
wrote...

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: forest@alittletooquiet.net, tvboxspy@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues
Date: Sun, 13 Jul 2014 12:36:47 -0700	[thread overview]
Message-ID: <20140713193647.GA31010@kroah.com> (raw)
In-Reply-To: <1405278681-3348-1-git-send-email-peter.senna@gmail.com>

On Sun, Jul 13, 2014 at 09:11:18PM +0200, Peter Senna Tschudin wrote:
> This patch cleanup coding style issues reported by checkpatch.
> 
> Tested by compilation only.
> 
> Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
> ---
> Cahnges from V1:
>  - Sent all patches in a series

Why did you forget the other thing that I asked you to change?

I can't take these as-is, sorry, please go back and re-read what I
wrote...

greg k-h

  parent reply	other threads:[~2014-07-13 19:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 19:11 [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues Peter Senna Tschudin
2014-07-13 19:11 ` Peter Senna Tschudin
2014-07-13 19:11 ` [PATCH V2 2/4] " Peter Senna Tschudin
2014-07-13 19:11   ` Peter Senna Tschudin
2014-07-13 19:11 ` [PATCH V2 3/4] " Peter Senna Tschudin
2014-07-13 19:11   ` Peter Senna Tschudin
2014-07-13 19:11 ` [PATCH V2 4/4] " Peter Senna Tschudin
2014-07-13 19:11   ` Peter Senna Tschudin
2014-07-13 19:36 ` Greg KH [this message]
2014-07-13 19:36   ` [PATCH V2 1/4] " Greg KH
2014-07-14  8:59   ` Peter Senna Tschudin
2014-07-14  8:59     ` Peter Senna Tschudin
2014-07-14 12:58     ` Greg KH
2014-07-14 12:58       ` Greg KH
2014-07-14 14:03       ` Peter Senna Tschudin
2014-07-14 14:03         ` Peter Senna Tschudin
2014-07-14 14:12     ` Dan Carpenter
2014-07-14 14:12       ` Dan Carpenter
2014-07-14 17:01       ` Peter Senna Tschudin
2014-07-14 17:01         ` Peter Senna Tschudin
2014-07-14 17:09         ` Dan Carpenter
2014-07-14 17:09           ` Dan Carpenter
2014-07-14 17:26         ` Greg KH
2014-07-14 17:26           ` Greg KH

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=20140713193647.GA31010@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=forest@alittletooquiet.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    --cc=tvboxspy@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.