From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ASoC: Cyclic dependency between soc.h and soc-dapm.h
Date: Wed, 17 Nov 2010 18:44:11 +0000 [thread overview]
Message-ID: <20101117184411.GE19488@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4CE3E7AE.7040308@metafoo.de>
On Wed, Nov 17, 2010 at 03:33:18PM +0100, Lars-Peter Clausen wrote:
[Reflowed into 80 columns, please look into your MUA configuration.]
> So I wonder if soc-dapm.h should be made completely internal and not
> be included anywhere else but soc.h anymore?
I think this is the simplest approach - the separation is useful for
code legibility but I don't think it's going to make a meanigful
difference if you always end up with both at compile time.
prev parent reply other threads:[~2010-11-17 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 14:33 ASoC: Cyclic dependency between soc.h and soc-dapm.h Lars-Peter Clausen
2010-11-17 18:44 ` Mark Brown [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=20101117184411.GE19488@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=lrg@slimlogic.co.uk \
/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).