From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] thinkpad-acpi: fix link error to include sound arch
Date: Sun, 7 Feb 2010 18:05:06 -0200 [thread overview]
Message-ID: <20100207200506.GA25736@khazad-dum.debian.net> (raw)
In-Reply-To: <73f3c62cccfd75cb045a352320346c26@localhost>
On Tue, 19 Jan 2010, Hagen Paul Pfeifer wrote:
> 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
This is not supposed to be possible anymore, and in fact, I can't force
that breakage to happen in 2.6.33-rc6.
> 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
Currently, the Kconfig disables ALSA support for thinkpad-acpi static
and ALSA as module, but allows static-static or module-module.
> Any other ideas Henrique?
No, you're correct, but the fix was already in its way to mainline when
you sent your report. I took some time to try to break it today, just
in case there was something I missed.
What kernel was giving you trouble? I still need to fix the backports in
the thinkpad-acpi git tree, maybe it was one of them?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2010-02-08 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 13:15 Hagen Paul Pfeifer
2010-01-19 14:51 ` Henrique de Moraes Holschuh
2010-01-19 15:07 ` Hagen Paul Pfeifer
2010-02-07 20:05 ` Henrique de Moraes Holschuh [this message]
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=20100207200506.GA25736@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=hagen@jauu.net \
--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
all inboxes | Powered by JetHome®