From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH 1/2] CHROMIUM: ASoC: Tegra: Move utilities to separate module
Date: Fri, 25 Feb 2011 11:52:41 +0000 [thread overview]
Message-ID: <20110225115241.GC28980@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1298420637-9230-1-git-send-email-swarren@nvidia.com>
On Tue, Feb 22, 2011 at 05:23:56PM -0700, Stephen Warren wrote:
> The utilities will be required by every machine driver. Including the
> utility object directly into every machine driver causes a build failure
> if the modules are actually built into the kernel, since each will define
> the symbols exported by the utility file. Solve this by moving the
> utility object into a separate module.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Applied, thanks.
prev parent reply other threads:[~2011-02-25 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 0:23 [PATCH 1/2] CHROMIUM: ASoC: Tegra: Move utilities to separate module Stephen Warren
2011-02-23 0:23 ` [PATCH 2/2] ASoC: WM8903: Fix double-applied patch Stephen Warren
2011-02-23 0:43 ` Stephen Warren
2011-02-23 21:15 ` [PATCH 1/2] CHROMIUM: ASoC: Tegra: Move utilities to separate module Liam Girdwood
2011-02-25 11:52 ` 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=20110225115241.GC28980@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=swarren@nvidia.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).