From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Adrian Bunk <bunk@fs.tum.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Re: [2.5 patch] ALSA: remove #if'd kernel 2.2 code
Date: Mon, 20 Jan 2003 10:47:15 +0100 [thread overview]
Message-ID: <s5hbs2c5f18.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301182128590.1425-100000@pnote.perex-int.cz>
At Sat, 18 Jan 2003 21:32:50 +0100 (CET),
Jaroslav wrote:
>
> On Fri, 17 Jan 2003, Adrian Bunk wrote:
>
> > Hi Jaroslav,
> >
> > the patch below removes #if'd code for kernel 2.2 (and in one place for
> > kernel < 2.4.18) from ALSA.
> >
> > I've tested the compilation with 2.5.59.
> >
> > Please apply
>
> Nice patch, but we turn in the maintaince nightmare, because our CVS tree
> contains shared sources among all kernels. I'll give a look what I can do
> to remove this code.
many of them had been already done on the cvs.
i'll check them now, too.
Jaroslav, could you sync with 2.5 tree and submit the patches to
Linus (even before pnp-merge)? otherwise we'll have again a mega-giga
patchset :)
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-20 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 15:56 [2.5 patch] ALSA: remove #if'd kernel 2.2 code Adrian Bunk
2003-01-18 20:32 ` Jaroslav Kysela
2003-01-20 9:47 ` Takashi Iwai [this message]
2003-01-21 11:11 ` Jaroslav Kysela
2003-01-21 11:15 ` Takashi Iwai
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=s5hbs2c5f18.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@fs.tum.de \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.