From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Bogicevic Sasa <brutallesale@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{'
Date: Sat, 31 Oct 2015 13:15:30 +0530 [thread overview]
Message-ID: <20151031074530.GD5145@sudip-pc> (raw)
In-Reply-To: <1446215456-25229-1-git-send-email-brutallesale@gmail.com>
On Fri, Oct 30, 2015 at 03:30:56PM +0100, Bogicevic Sasa wrote:
> This fixes "Blank lines aren't necessary after an open brace '{'"
> message from checkpatch.pl
>
> Signed-off-by: Bogicevic Sasa <brutallesale@gmail.com>
> ---
You are still using some other tree. This will not apply because of some
other change.
regards
sudip
next prev parent reply other threads:[~2015-10-31 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 14:30 [PATCH] drivers:staging:gdm724x Fix Blank lines aren't necessary after an open brace '{' Bogicevic Sasa
2015-10-31 7:45 ` Sudip Mukherjee [this message]
2015-10-31 23:58 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2015-10-30 15:13 Bogicevic Sasa
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=20151031074530.GD5145@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=brutallesale@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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