From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: coding style fixes
Date: Tue, 14 Jul 2015 13:26:53 +0000 [thread overview]
Message-ID: <20150714131453.GB18186@sudip-PC> (raw)
In-Reply-To: <1436856371-4570-1-git-send-email-simhavcs@gmail.com>
On Tue, Jul 14, 2015 at 12:16:11PM +0530, Vinay Simha BN wrote:
> kernel coding style fixes for below messages from
> scripts/checkpatch.pl
>
> WARNING: line over 80 character
> WARNING: Possible unnecessary 'out of memory' message
> WARNING: unnecessary whitespace before a quoted newline
> WARNING: Avoid line continuations in quoted strings
> ERROR: "foo * bar" should be "foo *bar"
> ERROR: do not initialise globals to 0 or NULL
These are too many changes in a single patch. Please only do one change
in a patch. And your patch is not applying also for a change done by
eb0f4271ca18 ("drivers: staging: sm750fb: Fix "'foo * bar' should be
'foo *bar'" errors")
Please refresh your patch against staging-testing tree.
regards
sudip
prev parent reply other threads:[~2015-07-14 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 6:58 [PATCH] staging: sm750fb: coding style fixes Vinay Simha BN
2015-07-14 13:26 ` 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=20150714131453.GB18186@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).