From: David Miller <davem@redhat.com>
To: amitg.b14@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: Fix coding style warnings and errors.
Date: Thu, 19 May 2016 11:48:59 -0700 (PDT) [thread overview]
Message-ID: <20160519.114859.762858537783024404.davem@redhat.com> (raw)
In-Reply-To: <1463534190-3327-1-git-send-email-amitg.b14@gmail.com>
From: Amit Ghadge <amitg.b14@gmail.com>
Date: Wed, 18 May 2016 06:46:30 +0530
> This is a patch to clean checkpatch warnings and errors
> in the Space.c file.
> Clean up the following warnings and errors.
>
> WARNING :
> * Block comments use * on subsequent lines
> * Missing a blank line after declarations
> * networking block comments don't use an empty /* line, use /*
> * please, no space before tabs
> * please, no spaces at the start of a line
> * line over 80 characters
>
> ERROR :
> * code indent should use tabs where possible
> * space prohibited after that open parenthesis '('
>
> Signed-off-by: Amit Ghadge <amitg.b14@gmail.com>
Applied.
prev parent reply other threads:[~2016-05-19 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 1:16 [PATCH v2] net: Fix coding style warnings and errors Amit Ghadge
2016-05-19 18:48 ` David Miller [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=20160519.114859.762858537783024404.davem@redhat.com \
--to=davem@redhat.com \
--cc=amitg.b14@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).