All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Levente Kurusa <levex@linux.com>
Cc: "Michał Kwiatkowski" <michaelflowersky@geekingspree.com>,
	devel@driverdev.osuosl.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"John Stultz" <john.stultz@linaro.org>,
	"Cruz Bishop" <cruzjbishop@gmail.com>,
	dan.carpenter@oracle.com
Subject: Re: [PATCH] Staging: android: fix parentheses coding style issue in alarm-dev.c
Date: Tue, 14 Jan 2014 13:58:42 -0800	[thread overview]
Message-ID: <20140114215842.GA4808@kroah.com> (raw)
In-Reply-To: <CAAsK9AG0J_+f+DPZ-j9uYJ9gPLkxG8ZGa20Poa2rLdUvb7-F_w@mail.gmail.com>

On Tue, Jan 14, 2014 at 10:43:04PM +0100, Levente Kurusa wrote:
> Hello,
> 
> 2014/1/14 Michał Kwiatkowski <michaelflowersky@geekingspree.com>:
> > From: Michal Kwiatkowski <michaelflowersky@geekingspree.com>
> >
> > This is a patch to the alarm-dev.c file that removes parentheses which
> > should not appear in return statement. This error was found by the
> > checkpatch.pl tool.
> >
> > Signed-off-by: Michał Kwiatkowski <michaelflowersky@geekingspree.com>
> > --
> 
> This is like the third patch in this two week period that does the
> exact same with more or less success, and I recall one getting applied
> (I might be wrong). Anyway, this one finally looks good! :-)

You are right, it doesn't apply, Michal should have received my
rejection notice from my patch-bot already saying this.

thanks,

greg k-h

  reply	other threads:[~2014-01-14 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 21:28 [PATCH] Staging: android: fix parentheses coding style issue in alarm-dev.c Michał Kwiatkowski
2014-01-14 21:43 ` Levente Kurusa
2014-01-14 21:58   ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-15 23:32 Michał Kwiatkowski
2014-01-16 17:51 ` Levente Kurusa

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=20140114215842.GA4808@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cruzjbishop@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=john.stultz@linaro.org \
    --cc=levex@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelflowersky@geekingspree.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.