[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140714085932.GA2958@hp-peter.rsr.lip6.fr>
Date: Mon, 14 Jul 2014 10:59:32 +0200
From: Peter Senna Tschudin <peter.senna@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Peter Senna Tschudin <peter.senna@...il.com>,
forest@...ttletooquiet.net, tvboxspy@...il.com,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH V2 1/4] staging: vt6556: Cleanup coding style issues
On Sun, Jul 13, 2014 at 12:36:47PM -0700, Greg KH wrote:
> 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@...il.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...
Actually I was trying to do what you asked me on this E-mail:
-- // --
You just sent me 4 patches, all with the same subject (but at least 2 of
them had the order in which to apply them in, which is nice.)
Please redo these such that they have a unique subject, and I can tell
which order to apply them in, as I really have no idea about the second
two.
-- // --
I'm sending V3 as a single patch.
>
> greg k-h
View attachment "0001-staging-vt6556-Cleanup-coding-style-issues.patch" of type "text/plain" (15553 bytes)
Powered by blists - more mailing lists