From: Takashi Iwai <tiwai@suse.de>
To: Martin Langer <martin-langer@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: kernel 2.2
Date: Thu, 08 Jan 2004 12:02:10 +0100 [thread overview]
Message-ID: <s5hptduzost.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040107223844.GA15133@tuba.home>
At Wed, 7 Jan 2004 23:38:44 +0100,
Martin Langer wrote:
>
>
> I have two warnings with 2.2. The first one is still not fixed:
>
> pci_compat_22.c: In function snd_pci_compat_release_region':
> pci_compat_22.c:384: warning: implicit declaration of function
> release_mem_region'
>
>
> ... and the second one needs this fix:
i fixed them (hopefully) now.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
prev parent reply other threads:[~2004-01-08 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 22:38 kernel 2.2 Martin Langer
2004-01-08 11:02 ` Takashi Iwai [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=s5hptduzost.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=martin-langer@gmx.de \
/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