From: Greg KH <gregkh@linuxfoundation.org>
To: Dzonatans Melgalvis <dz.melgalvis@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: comedidev.h: fix checkpatch code style issue
Date: Tue, 5 Aug 2014 16:35:07 -0700 [thread overview]
Message-ID: <20140805233507.GA27293@kroah.com> (raw)
In-Reply-To: <1407281385-12576-1-git-send-email-dz.melgalvis@gmail.com>
On Wed, Aug 06, 2014 at 02:29:45AM +0300, Dzonatans Melgalvis wrote:
> Fixing checkpatch warning - blank line missing after declaration.
>
> Signed-off-by: Dzonatans Melgalvis <dz.melgalvis@gmail.com>
> ---
> drivers/staging/comedi/comedidev.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/staging/comedi/comedidev.h b/drivers/staging/comedi/comedidev.h
> index 58e58a3..c9b7978 100644
> --- a/drivers/staging/comedi/comedidev.h
> +++ b/drivers/staging/comedi/comedidev.h
> @@ -57,6 +57,7 @@ struct comedi_subdevice {
> const unsigned int *maxdata_list; /* list is channel specific */
>
> const struct comedi_lrange *range_table;
> +
> const struct comedi_lrange *const *range_table_list;
Really? Why add that one? Shouldn't you just remove the previous line?
>
> unsigned int *chanlist; /* driver-owned chanlist (not used) */
> @@ -207,8 +208,10 @@ struct comedi_async {
> struct comedi_cmd cmd;
> wait_queue_head_t wait_head;
> unsigned int cb_mask;
> +
> int (*inttrig)(struct comedi_device *dev, struct comedi_subdevice *s,
> unsigned int x);
> +
> };
Why is that last line needed?
Please use your judgement with checkpatch fixes, this patch isn't ok
as-is, sorry.
greg k-h
next prev parent reply other threads:[~2014-08-05 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 23:29 [PATCH] Staging: comedi: comedidev.h: fix checkpatch code style issue Dzonatans Melgalvis
2014-08-05 23:35 ` Greg KH [this message]
2014-08-06 2:31 ` Joe Perches
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=20140805233507.GA27293@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dz.melgalvis@gmail.com \
--cc=linux-kernel@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