From: Lee Revell <rlrevell@joe-job.com>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: io_remap_page_range (was Re: [Alsa-devel] alsa-driver will not compile with kernel 2.6.9-rc2-mm4-S7)
Date: Fri, 01 Oct 2004 20:51:08 -0400 [thread overview]
Message-ID: <1096678268.27818.84.camel@krustophenia.net> (raw)
In-Reply-To: <32868.192.168.1.8.1096677269.squirrel@192.168.1.8>
On Fri, 2004-10-01 at 20:34, Rui Nuno Capela wrote:
> Lee Revell wrote:
> Good grief! I'm having this too, and I was desperate thinking I was the
> only one, and ultimately offering the blame to gcc 3.4.1 which is what I'm
> test-driving now on my laptop (Mdk 10.1c).
>
> Now I remember that -mm4 has some issue about remap_page_range kernel
> symbol being renamed to something else, which is breaking the build of
> outsider modules (i.e. not the ones bundled under the kernel source tree).
> Or so it seems.
Looking through my archives I cannot find a report of this exact issue,
but you are probably right. Looks like ALSA drivers need to be updated.
Lee
next prev parent reply other threads:[~2004-10-02 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-02 0:12 alsa-driver will not compile with kernel 2.6.9-rc2-mm4-S7 Lee Revell
2004-10-02 0:34 ` [Alsa-devel] " Rui Nuno Capela
2004-10-02 0:48 ` Tonnerre
2004-10-02 0:53 ` Lee Revell
2004-10-02 1:13 ` Lee Revell
2004-10-02 1:23 ` Lee Revell
2004-10-02 0:51 ` Lee Revell [this message]
2004-10-04 15:26 ` io_remap_page_range (was Re: [Alsa-devel] alsa-driver will not compile with kernel 2.6.9-rc2-mm4-S7) Takashi Iwai
2004-10-08 19:23 ` Lee Revell
2004-10-08 20:11 ` Lee Revell
2004-10-02 11:47 ` [Alsa-devel] alsa-driver will not compile with kernel 2.6.9-rc2-mm4-S7 Florian Schmidt
2004-10-02 12:25 ` Florian Schmidt
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=1096678268.27818.84.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rncbc@rncbc.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