All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: AF9035 experimental header changes
Date: Sun, 13 May 2012 20:39:35 +0300	[thread overview]
Message-ID: <4FAFF1D7.6070700@iki.fi> (raw)
In-Reply-To: <4FAFEED8.7080903@schinagl.nl>

On 13.05.2012 20:26, Oliver Schinagl wrote:
> On 13-05-12 17:51, Antti Palosaari wrote:
>> On 13.05.2012 18:24, Oliver Schinagl wrote:
>>> Hi antti,
>>>
>>> I've just updated my local branch of your experimental branch and got
>>> some conflicts because you moved the header inclusions from the C file
>>> to the header file. Why is that? I thought it was really bad practice to
>>> have includes in header files.
>>>
>>> http://git.linuxtv.org/anttip/media_tree.git/commitdiff/7d28d8226cffd1ad6e555b36f6f9855d8bba8645
>>>
>>
>> Because "struct state" was inside af9013.h and I added "struct
>> af9033_config" to state. Due to that af9033_config visibility I was
>> forced to move af9013.h include to the af9015.h and moved all the
>> others too.
>>
> I see, I just learnedthat having includes in headers is just something
> really bad, possibly causing include loops etc etc. Its just something
> that's generally not needed and should be avoided. ideally anyway :)

But it is not actual header in the mind of the normal header. It is 
something like driver private include. Maybe better name could be 
af9035_priv.h as the demodulators files are named. But as all the other 
DVB USB drivers are named without priv I do not like to name that 
differently.

Include guards [1] are for avoiding include loops.

>> What is problem you has met?
> Well it's just movement of those headers caused merges to conflict and
> fail :)

Hmmm, may I ask what you are doing? Adding some new supported tuners or 
hacking dual mode?

That my repository is the only "official" one. As that is the official 
repo you should resolve merge conflicts with your own :)

>> DVB USB driver header file is something like private place for data
>> other than code as it is not included by any other driver.

[1] http://en.wikipedia.org/wiki/Include_guard

regards
Antti
-- 
http://palosaari.fi/

      reply	other threads:[~2012-05-13 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 15:24 AF9035 experimental header changes Oliver Schinagl
2012-05-13 15:51 ` Antti Palosaari
2012-05-13 17:26   ` Oliver Schinagl
2012-05-13 17:39     ` Antti Palosaari [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=4FAFF1D7.6070700@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.