From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aniruddha Shastri <aniruddha.shastri@gmail.com>
Cc: devel@driverdev.osuosl.org,
"Christopher Mårtensson" <cribalik@gmail.com>,
linux-kernel@vger.kernel.org, "Ian Abbott" <abbotti@mev.co.uk>,
"Saber Rezvani" <irsaber@gmail.com>,
"Matthew Giassa" <matthew@giassa.net>,
"Karthik Nayak" <karthik.188@gmail.com>
Subject: Re: [PATCH] staging: comedi: ni_*
Date: Wed, 13 Dec 2017 13:07:33 +0100 [thread overview]
Message-ID: <20171213120733.GA3402@kroah.com> (raw)
In-Reply-To: <CANChdViW8N88-0oVWaehLR7MBNnJj9RCbQAEGU4f5oTca+NsYg@mail.gmail.com>
On Wed, Dec 13, 2017 at 05:16:13PM +0530, Aniruddha Shastri wrote:
> On Wed, Dec 13, 2017 at 4:20 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Dec 13, 2017 at 04:01:04AM -0600, Aniruddha Shastri wrote:
> > > Fix checkpatch warnings by shortening lines and reorganizing code where needed..
> > > Re-phrase the assert messages in ni_mio_common.c. This was done to meet the character limit for the message.
> >
> > And yet this line is over the character length :)
> Aniruddha: Thanks for pointing this out, I'll amend the commit message. :)
Why put your name in the response? Of course I know it's you who is
writing this :)
> > > range_table_list = kmalloc_array(32,
> > > - sizeof(struct comedi_lrange *),
> > > + range_size,
> >
> > Not worth changing.
>
> Aniruddha: The original checkpatch.pl warning instructed to use
> const struct comedi_lrange instead of struct. Adding the 'const' put this
> line over the limit, so that's why I pulled it out into a local variable.
Checkpatch is a "hint", don't always follow it, it can cause some code
to look really bad. It's not a hard-rule.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-13 12:07 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 [this message]
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
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=20171213120733.GA3402@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=irsaber@gmail.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