linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pinkesh Jain <pinkeshbadjatiya@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	carlos@cgarcia.org, linux-wireless@vger.kernel.org,
	rickard_strandqvist@spectrumdigital.se, luca@lucaceresoli.net,
	Jes.Sorensen@redhat.com, Larry.Finger@lwfinger.net,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	gdonald@gmail.com
Subject: Re: [PATCH] Removed extra spaces, and error from checkpatch.pl
Date: Sun, 27 Sep 2015 08:03:47 -0700	[thread overview]
Message-ID: <20150927150347.GA27003@kroah.com> (raw)
In-Reply-To: <CACJZ1zqyVJ95GNWReSZ-C3hgjgA97LaJNna=pGkKC8ZQjzvnuA@mail.gmail.com>

On Sun, Sep 27, 2015 at 01:59:17PM +0530, Pinkesh Jain wrote:
> There were many warnings and error given by checkpatch.pl and most of them were
> almost of the same type so i believed a single patch is enough to do the
> cleanup.
> 
> 1. Remove errors of the struct declaration (foo*bar to foo *bar)
> 2. Removed warnings of 'spaces before comma'.
> 3. Added space after enum declaration and before opening of paranthesis.
> 4. removed spaces between function calls (func () to func() )
> 5. Still there are a lot of warnings related to only line lengths but removing
> then would not make sense and would leave the code unreadable.
> 
> There were one or two more of such kind of very small code refactoring that i
> did. Since they were not that important, also i 'Did Not Alter' any other part
> of functioning code so i made the changes in a single patch.
> 
> I am new here and this is my first patch so please give me  enough suggestions
> and reviews for what i do, so that i can get familiar with the community
> guidelines.
> 
> If i do anything wrong then please correct me.
> 
> Questions:
> 1.) Do i need to mention all this changes that i wrote about in the commit as
> they are very descriptive? I tried to be brief in the commit message.

Be descriptive.

> 2.) Do i need to split the changes in separate commits, as one of the members
> pointed out.

yes.

      parent reply	other threads:[~2015-09-27 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27  0:14 [PATCH] Removed extra spaces, and error from checkpatch.pl Pinkesh Badjatiya
2015-09-27  2:25 ` Jes Sorensen
2015-09-27  6:03 ` Sudip Mukherjee
     [not found]   ` <CACJZ1zqyVJ95GNWReSZ-C3hgjgA97LaJNna=pGkKC8ZQjzvnuA@mail.gmail.com>
2015-09-27 15:03     ` 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=20150927150347.GA27003@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jes.Sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=carlos@cgarcia.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gdonald@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=pinkeshbadjatiya@gmail.com \
    --cc=rickard_strandqvist@spectrumdigital.se \
    --cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).