public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aniruddha Shastri <aniruddha.shastri@gmail.com>
Cc: "Ian Abbott" <abbotti@mev.co.uk>,
	"H Hartley Sweeten" <hsweeten@visionengravers.com>,
	"Matthew Giassa" <matthew@giassa.net>,
	"Christopher Mårtensson" <cribalik@gmail.com>,
	"Karthik Nayak" <karthik.188@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: comedi: ni_*: Fix style warnings.
Date: Tue, 19 Dec 2017 14:59:55 +0100	[thread overview]
Message-ID: <20171219135955.GA32322@kroah.com> (raw)
In-Reply-To: <1513236675-62337-1-git-send-email-aniruddha.shastri@gmail.com>

On Thu, Dec 14, 2017 at 01:31:05AM -0600, Aniruddha Shastri wrote:
> Two of these warnings are now line-too-long warnings. I think these 
> warnings are preferable to the ones listed below. The longest line is
> only 85 chars wide, which is reasonable.
> 
> Warnings fixed:
> ni_atmio.c:239: WARNING: Avoid multiple line dereference
> 	- prefer 'ni_boards[i].isapnp_id'
> ni_labpc_common.c:573: WARNING: Avoid multiple line dereference
> 	- prefer 'cmd->scan_begin_arg'
> ni_mio_common.c:736: WARNING: Avoid multiple line dereference
> 	- prefer 'devpriv->counter_dev->counters[gpct_index]'
> ni_mio_common.c:1977: WARNING: Prefer using '"%s...", __func__'
> 	to using 'ni_cmd_set_mite_transfer', this function's name, in a string
> ni_mio_common.c:1990: WARNING: Prefer using '"%s...", __func__'
> 	to using 'ni_cmd_set_mite_transfer', this function's name, in a string
> ni_mio_common.c:4302: WARNING: function definition argument
> 	'int' should also have an identifier name
> ni_mio_common.c:4302: WARNING: function definition argument
> 	'int' should also have an identifier name
> ni_mio_common.c:4302: WARNING: function definition argument
> 	'int *' should also have an identifier name
> ni_mio_common.c:4699: WARNING: Prefer using '"%s...", __func__'
> 	to using 'cs5529_do_conversion', this function's name, in a string
> ni_stc.h:21: WARNING: Block comments should align the * on each line
> 
> Signed-off-by: Aniruddha Shastri <aniruddha.shastri@gmail.com>
> ---
> Changes in v3:
> No longer add 'const' to sizeof(struct comedi_lrange) in ni_670x.c:212

Please only fix one "type" of issue per patch.  This should be broken up
into multiple patches and sent as a patch series.

thanks,

greg k-h

  reply	other threads:[~2017-12-19 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 10:01 [PATCH] staging: comedi: ni_* Aniruddha Shastri
2017-12-13 10:50 ` Greg Kroah-Hartman
2017-12-13 11:46   ` Aniruddha Shastri
2017-12-13 12:07     ` Greg Kroah-Hartman
2017-12-14  6:27       ` [PATCH v2] staging: comedi: ni_*: Fix style warnings Aniruddha Shastri
2017-12-14  6:48         ` Joe Perches
2017-12-14  7:31           ` [PATCH v3] " Aniruddha Shastri
2017-12-19 13:59             ` Greg Kroah-Hartman [this message]
2017-12-14  7:48       ` [PATCH] staging: comedi: ni_* Aniruddha Shastri

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=20171219135955.GA32322@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=aniruddha.shastri@gmail.com \
    --cc=cribalik@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hsweeten@visionengravers.com \
    --cc=karthik.188@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@giassa.net \
    /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