From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Senna Tschudin <peter.senna@gmail.com>
Cc: swetland@google.com, daniel@ffwll.ch,
maarten.lankhorst@canonical.com, john.stultz@linaro.org,
sumit.semwal@linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: android: Cleanup style issues
Date: Sat, 12 Jul 2014 20:24:15 +0000 [thread overview]
Message-ID: <20140712202415.GA10041@kroah.com> (raw)
In-Reply-To: <20140712202310.GA9919@kroah.com>
On Sat, Jul 12, 2014 at 01:23:10PM -0700, Greg KH wrote:
> On Sat, Jul 12, 2014 at 09:55:56PM +0200, Peter Senna Tschudin wrote:
> > This patch fixes the following checkpatch warnings:
> > - Remove else after return
> > - Add space after declaration
> >
> > Tested by compilation only.
> >
> > Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
> > ---
> > drivers/staging/android/sync_debug.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
>
> This file is no longer in my kernel tree, what tree did you make it
> against?
>
> Please create staging patches against the staging-next branch of the
> staging.git tree on git.kernel.org so that I can apply them.
Ah, nevermind, things moved around here, I figured this out, sorry for
the noise...
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: swetland@google.com, daniel@ffwll.ch,
maarten.lankhorst@canonical.com, john.stultz@linaro.org,
sumit.semwal@linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging: android: Cleanup style issues
Date: Sat, 12 Jul 2014 13:24:15 -0700 [thread overview]
Message-ID: <20140712202415.GA10041@kroah.com> (raw)
In-Reply-To: <20140712202310.GA9919@kroah.com>
On Sat, Jul 12, 2014 at 01:23:10PM -0700, Greg KH wrote:
> On Sat, Jul 12, 2014 at 09:55:56PM +0200, Peter Senna Tschudin wrote:
> > This patch fixes the following checkpatch warnings:
> > - Remove else after return
> > - Add space after declaration
> >
> > Tested by compilation only.
> >
> > Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
> > ---
> > drivers/staging/android/sync_debug.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
>
> This file is no longer in my kernel tree, what tree did you make it
> against?
>
> Please create staging patches against the staging-next branch of the
> staging.git tree on git.kernel.org so that I can apply them.
Ah, nevermind, things moved around here, I figured this out, sorry for
the noise...
greg k-h
next prev parent reply other threads:[~2014-07-12 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 19:55 [PATCH] staging: android: Cleanup style issues Peter Senna Tschudin
2014-07-12 19:55 ` Peter Senna Tschudin
2014-07-12 20:23 ` Greg KH
2014-07-12 20:23 ` Greg KH
2014-07-12 20:24 ` Greg KH [this message]
2014-07-12 20:24 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2014-07-19 12:14 [PATCH] staging: android: cleanup " Elias Boutaleb
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=20140712202415.GA10041@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=john.stultz@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=peter.senna@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=swetland@google.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.