From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Seungwhan Youn <claude.youn@gmail.com>
Cc: alsa-devel@alsa-project.org,
Jassi Brar <jassisinghbrar@gmail.com>,
lrg@slimlogic.co.uk, jassi.brar@samsung.com,
Seungwhan Youn <sw.youn@samsung.com>
Subject: Re: [PATCH 4/4] ASoC: SAMSUNG: Clean-up header includes
Date: Fri, 7 Jan 2011 10:38:56 +0000 [thread overview]
Message-ID: <20110107103855.GA9209@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikZQcxG85Ebjbf_gXbe_VBX-o8Zsg=QdUnuDUhB@mail.gmail.com>
On Fri, Jan 07, 2011 at 04:03:46PM +0900, Seungwhan Youn wrote:
> As you know, 'include/sound/soc.h' has some general linux's includes.
> So I made these sequence to prevent dependency problem, because
> reverse including could have some problem, if linux's includes has
> their dependencies.
If there's dependency problems in the core headers we should just fix
those, users shouldn't need to worry about that sort of stuff.
next prev parent reply other threads:[~2011-01-07 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 4:43 [PATCH 0/4] ASoC: SAMSUNG: Code clean-up suitable for current ASoC Seungwhan Youn
2011-01-07 4:46 ` [PATCH 1/4] ASoC: SAMSUNG: Remove AC97 header file Seungwhan Youn
2011-01-07 4:51 ` [PATCH 2/4] ASoC: SAMSUNG: Clean-up DMA " Seungwhan Youn
2011-01-07 6:03 ` Jassi Brar
2011-01-07 6:02 ` [PATCH 1/4] ASoC: SAMSUNG: Remove AC97 " Jassi Brar
2011-01-07 4:57 ` [PATCH 3/4] ASoC: SAMSUNG: Move PCM specific definitions into pcm.c Seungwhan Youn
2011-01-07 6:04 ` Jassi Brar
2011-01-07 4:57 ` [PATCH 4/4] ASoC: SAMSUNG: Clean-up header includes Seungwhan Youn
2011-01-07 6:08 ` Jassi Brar
2011-01-07 7:03 ` Seungwhan Youn
2011-01-07 10:38 ` Mark Brown [this message]
2011-01-07 11:22 ` Seungwhan Youn
2011-01-10 22:26 ` [PATCH v2 " Seungwhan Youn
2011-01-11 10:51 ` Liam Girdwood
2011-01-11 11:26 ` Jassi Brar
2011-01-11 11:29 ` Mark Brown
2011-01-09 14:01 ` [PATCH 0/4] ASoC: SAMSUNG: Code clean-up suitable for current ASoC Liam Girdwood
2011-01-10 11:40 ` Mark Brown
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=20110107103855.GA9209@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=claude.youn@gmail.com \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=sw.youn@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).