From: Greg KH <gregkh@linuxfoundation.org>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
gamerh2o@gmail.com, mark.einon@gmail.com
Subject: Re: [PATCH] staging: bcm: multiple checkpatch fixes for InterfaceIdleMode.c
Date: Wed, 8 Oct 2014 15:40:09 -0700 [thread overview]
Message-ID: <20141008224009.GA9464@kroah.com> (raw)
In-Reply-To: <1412097977-3254-1-git-send-email-karthik.188@gmail.com>
On Tue, Sep 30, 2014 at 10:56:17PM +0530, Karthik Nayak wrote:
> 1. WARNING: else is not generally useful after a break or return
>
> 2. WARNING: quoted string split across lines
>
> 3. WARNING: break quoted strings at a space character
>
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---
> drivers/staging/bcm/InterfaceIdleMode.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
Doesn't apply to my tree :(
prev parent reply other threads:[~2014-10-08 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:26 [PATCH] staging: bcm: multiple checkpatch fixes for InterfaceIdleMode.c Karthik Nayak
2014-09-30 18:52 ` Mark Einon
2014-10-08 22:40 ` Greg KH [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=20141008224009.GA9464@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gamerh2o@gmail.com \
--cc=karthik.188@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.einon@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox