From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hartley Sweeten <HartleyS@visionengravers.com>
Cc: Ian Abbott <abbotti@mev.co.uk>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] staging: comedi: comedidev.h: fix some checkpatch issues
Date: Mon, 12 Oct 2015 10:25:51 -0700 [thread overview]
Message-ID: <20151012172551.GA8815@kroah.com> (raw)
In-Reply-To: <BN3PR0101MB1057D7236CA9B2CDFBFBC119D0310@BN3PR0101MB1057.prod.exchangelabs.com>
On Mon, Oct 12, 2015 at 05:22:29PM +0000, Hartley Sweeten wrote:
> On Monday, October 12, 2015 10:03 AM, Ian Abbott wrote:
> > Fix some checkpatch issues in "comedidev.h". There are still some
> > CamelCase warnings, but since those are for the use of "mA" and it
> > represents "milliamps", I think I'll leave them alone.
> >
> > 1) staging: comedi: comedidev.h: add comments to spin-lock and mutex
> > 2) staging: comedi: comedidev.h: spaces preferred around that '*'
> >
> > drivers/staging/comedi/comedidev.h | 18 +++++++++---------
> > 1 file changed, 9 insertions(+), 9 deletions(-)
>
> Thanks!
>
> Reviewed-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>
> Ian,
>
> Just a comment...
>
> The checkpaatch.pl noise about "mA" defines are a bit annoying but
> I agree that those defines are clearer than "{foo}_milliamps".
I agree, checkpatch is just a "hint", feel free to ignore it when it
says stupid things. Like this.
thanks,
greg k-h
prev parent reply other threads:[~2015-10-12 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 17:03 [PATCH 0/2] staging: comedi: comedidev.h: fix some checkpatch issues Ian Abbott
2015-10-12 17:03 ` [PATCH 1/2] staging: comedi: comedidev.h: add comments to spin-lock and mutex Ian Abbott
2015-10-12 17:03 ` [PATCH 2/2] staging: comedi: comedidev.h: spaces preferred around that '*' Ian Abbott
2015-10-12 17:22 ` [PATCH 0/2] staging: comedi: comedidev.h: fix some checkpatch issues Hartley Sweeten
2015-10-12 17:25 ` Greg Kroah-Hartman [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=20151012172551.GA8815@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=HartleyS@visionengravers.com \
--cc=abbotti@mev.co.uk \
--cc=driverdev-devel@linuxdriverproject.org \
--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