mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@nxp.com>
To: "knaack.h@gmx.de" <knaack.h@gmx.de>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"rodrigosiqueiramelo@gmail.com" <rodrigosiqueiramelo@gmail.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] iio: apply coding-style into ms5611_probe function
Date: Fri, 16 Feb 2018 13:57:17 +0000	[thread overview]
Message-ID: <1518789437.9517.32.camel@nxp.com> (raw)
In-Reply-To: <20180216133841.3yt4ip3tbck7ihdm@smtp.gmail.com>

Hi Rodrigo,

Mostly looking good. Few comments.

Please read:

https://chris.beams.io/posts/git-commit/

1) Capitalize the first letter of commit
2) Use prefix tags to indicate the driver that is changed. Here iio:pressure:ms5611.

If not sure what prefix tags to use please use git log file.c and see the tags used by previous commits.
If not clear from previous commits be creative! :)

3) A better verb describing the change would be Fix instead of Apply.

So, the commit subject should be:

iio:pressure:ms5611: Fix coding style in probe function

4) Please correct all the occurences of the same coding style error (not sure if here is the case).

Other than that it looks good to me. Please send v2.

Do not forget to add under the scissor line of the new patch a small changelog documenting what
has changed since v1.



On Vi, 2018-02-16 at 11:38 -0200, rodrigosiqueira wrote:
> This patch fixes the checkpatch.pl warning and error:
> 
> iio/pressure/ms5611.h:66: ERROR: code indent should use tabs where possible
> iio/pressure/ms5611.h:66: WARNING: please, no spaces at the start of a line
> iio/pressure/ms5611.h:66: ERROR: "foo* bar" should be "foo *bar"
> 
> Signed-off-by: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
> ---
> 

^ this is the scissor line.

thanks,
Daniel.

      reply	other threads:[~2018-02-16 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 13:38 rodrigosiqueira
2018-02-16 13:57 ` Daniel Baluta [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=1518789437.9517.32.camel@nxp.com \
    --to=daniel.baluta@nxp.com \
    --cc=jic23@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=rodrigosiqueiramelo@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

Powered by JetHome