From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] thinkpad-acpi: fix link error to include sound arch
Date: Tue, 19 Jan 2010 16:07:24 +0100 [thread overview]
Message-ID: <73f3c62cccfd75cb045a352320346c26@localhost> (raw)
In-Reply-To: <20100119145108.GD2668@khazad-dum.debian.net>
On Tue, 19 Jan 2010 12:51:08 -0200, <hmh@hmh.eng.br> wrote:
> Can you describe the problem in more detail? That will save me precious
> time, as I am rather overworked right now...
If you build the sound as a module and thinkpad as a build-in component
the linker will complain about missing symbols. So the right fix may
be a patch that 1) enforces the sound component to be build static or
to enforces thinkpad apic to be build as a module. Another way 2) is
to separate the thinkpad sound component in a autonomous separate
module.
Any other ideas Henrique?
Hagen
next prev parent reply other threads:[~2010-01-19 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:15 [PATCH 1/1] thinkpad-acpi: fix link error to include sound arch Hagen Paul Pfeifer
2010-01-19 14:51 ` Henrique de Moraes Holschuh
2010-01-19 15:07 ` Hagen Paul Pfeifer [this message]
2010-02-07 20:05 ` Henrique de Moraes Holschuh
2010-02-20 9:47 ` Hagen Paul Pfeifer
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=73f3c62cccfd75cb045a352320346c26@localhost \
--to=hagen@jauu.net \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
/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