From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] coding style: Fix 1 error and 5 warnings
Date: Fri, 17 Jul 2015 05:44:44 +0000 [thread overview]
Message-ID: <20150717053244.GD3422@sudip-PC> (raw)
In-Reply-To: <1437062154-29181-1-git-send-email-antoine.blin@lip6.fr>
On Fri, Jul 17, 2015 at 10:52:59AM +0530, Sudip Mukherjee wrote:
> On Thu, Jul 16, 2015 at 05:55:54PM +0200, antoine wrote:
> > This is a patch to the ddk750_power.c file that fixes up five "line over 80
> > characters" warnings and one "return is not a function, parentheses are not
> > required" error found by the checkpatch.pl script.
> That becomes two different change. Please only do one type of change in
> one patch.
Forgot mentioning, please fix the subject also.
regards
sudip
prev parent reply other threads:[~2015-07-17 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:55 [PATCH] coding style: Fix 1 error and 5 warnings antoine
2015-07-17 5:34 ` Sudip Mukherjee
2015-07-17 5:44 ` Sudip Mukherjee [this message]
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=20150717053244.GD3422@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).