From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: LMML <linux-media@vger.kernel.org>, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [GIT PULL] SDR stuff
Date: Tue, 22 Jul 2014 04:05:05 +0300 [thread overview]
Message-ID: <53CDB8C1.8000203@iki.fi> (raw)
In-Reply-To: <20140721215140.35935811.m.chehab@samsung.com>
On 07/22/2014 03:51 AM, Mauro Carvalho Chehab wrote:
> Em Tue, 22 Jul 2014 03:08:19 +0300
> Antti Palosaari <crope@iki.fi> escreveu:
>
>> So what. Those were mostly WARNING only and all but long lines were some
>> new checks added to checkpatch recently. chekcpatch gets all the time
>> new and new checks, these were added after I have made that driver. I
>> will surely clean those later when I do some new changes to driver and
>> my checkpatch updates.
>
> Antti,
>
> I think you didn't read my comments in the middle of the checkpatch stuff.
> Please read my email again. I'm not requiring you to fix the newer checkpatch
> warning (Missing a blank line after declarations), and not even about the
> 80-cols warning. The thing is that there are two issues there:
>
> 1) you're adding API bits at msi2500 driver, instead of moving them
> to videodev2.h (or reusing the fourcc types you already added there);
If you look inside driver code, you will see those defines are not used
- but commented out. It is simply dead definition compiler optimizes
away. It is code I used on my tests, but finally decided to comment out
to leave some time add those later to API. I later moved 2 of those to
API, that is done in same patch serie.
No issue here.
> 2) you're handling jiffies wrong inside the driver.
>
> As you may know, adding a driver at staging is easier than at the main
> tree, as we don't care much about checkpatch issues (and not even about
> some more serious issues). However, when moving stuff out of staging,
> we review the entire driver again, to be sure that it is ok.
That jiffie check is also rather new and didn't exists time drive was
done. Jiffie is used to calculate debug sample rate. There is multiple
times very similar code piece, which could be optimized to one. My plan
merge all those ~5 functions to one and use jiffies using macros as
checkpatch now likes. I don't see meaningful fix it now as you are going
to rewrite that stuff in near future in any case.
Silencing all those checkpatch things is not very hard job though. If
you merge that stuff to media/master I can do it right away (I am
running older kernel and older checkpatch currently).
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2014-07-22 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 1:14 [GIT PULL] SDR stuff Antti Palosaari
2014-07-20 16:41 ` Antti Palosaari
2014-07-21 23:50 ` Mauro Carvalho Chehab
2014-07-22 0:05 ` Mauro Carvalho Chehab
2014-07-22 0:16 ` Antti Palosaari
2014-07-22 0:08 ` Antti Palosaari
2014-07-22 0:51 ` Mauro Carvalho Chehab
2014-07-22 1:05 ` Antti Palosaari [this message]
2014-07-22 2:09 ` Mauro Carvalho Chehab
2014-07-22 2:48 ` Antti Palosaari
2014-07-22 4:27 ` Mauro Carvalho Chehab
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=53CDB8C1.8000203@iki.fi \
--to=crope@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).