From: Dave Strauss <Dave.Strauss@zoran.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Darius Augulis <augulis.darius@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Paulius Zaleckas <paulius.zaleckas@teltonika.lt>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/5] CSI camera interface driver for MX1
Date: Thu, 26 Mar 2009 17:31:35 -0400 [thread overview]
Message-ID: <49CBF437.7030603@zoran.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0903262116410.5438@axis700.grange>
Guennadi Liakhovetski wrote:
> On Thu, 26 Mar 2009, Mauro Carvalho Chehab wrote:
>
>>>>> + /* common v4l buffer stuff -- must be first */
>>>>> + struct videobuf_buffer vb;
>>>>>
>>>> Here you have one space
>>>>
>>>>
>>>>> +
>>>>> + const struct soc_camera_data_format *fmt;
>>>>>
>>>> Here you have 8 spaces
>>>>
>>>>
>>>>> +
>>>>> + int inwork;
>>>>>
>>>> Here you have tabs. Please, unify.
>> Please always check your patches with checkpatch.pl. This will point such issues.
>
> No, I did check the patch with checkpatch.pl and it didn't complain about
> this. It checks _indentation_ of lines, that _must_ be done with TABs, but
> it doesn't check what is used for alignment _inside_ lines, like
>
> xxx = 0;
> y = 1;
> zzzzz = 2;
>
> where first and third lines have spaces before "=", and the second one has
> a TAB. This is not checked by checkpatch.pl.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski
>
Newbie question -- where does one find checkpatch.pl? And are there any other
tools we should be running on patches before we submit them?
Thanks.
- Dave Strauss
next prev parent reply other threads:[~2009-03-26 22:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49C89F00.1020402@gmail.com>
2009-03-26 18:59 ` [PATCH 1/5] CSI camera interface driver for MX1 Guennadi Liakhovetski
2009-03-26 19:19 ` Darius Augulis
2009-03-26 20:09 ` Mauro Carvalho Chehab
2009-03-26 20:19 ` Guennadi Liakhovetski
2009-03-26 21:31 ` Dave Strauss [this message]
2009-03-26 21:49 ` Mauro Carvalho Chehab
2009-03-26 22:07 ` Russell King - ARM Linux
2009-03-27 7:33 ` Holger Schurig
2009-03-27 8:25 ` Russell King - ARM Linux
2009-03-27 9:37 ` Darius Augulis
2009-03-27 10:34 ` Mauro Carvalho Chehab
2009-03-27 10:56 ` Mauro Carvalho Chehab
2009-03-27 13:39 ` Darius Augulis
2009-03-27 16:50 ` Mauro Carvalho Chehab
2009-03-27 15:18 ` Darius Augulis
2009-03-27 15:42 ` Russell King - ARM Linux
2009-03-27 15:55 ` Guennadi Liakhovetski
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=49CBF437.7030603@zoran.com \
--to=dave.strauss@zoran.com \
--cc=augulis.darius@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=paulius.zaleckas@teltonika.lt \
--cc=s.hauer@pengutronix.de \
/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