From: Greg KH <greg@kroah.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ALSA update
Date: Wed, 18 Dec 2002 11:27:40 -0800 [thread overview]
Message-ID: <20021218192740.GC32190@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212182013070.550-100000@pnote.perex-int.cz>
On Wed, Dec 18, 2002 at 08:17:55PM +0100, Jaroslav Kysela wrote:
>
> Not much. We have 9 #ifdef's and all trying to resolve the conflicts with
> new function prototypes which is difficult to replace with defines or
> inline functions. Perhaps, you'll have an idea to solve this problem.
Short of keeping a 2.4 version and a 2.5/2.6 version, no, I do not have
any ideas, sorry. The USB core has changed a lot between those two
trees, as you know.
> For us, it's very important to have only one code base for all kernels,
> but on the other hand, we're trying to leave the 2.2/2.4 kernel code
> specific parts separate in our CVS repository if possible.
Then you might want to leave the OLD_USB stuff out of the 2.5 kernel :)
thanks,
greg k-h
next prev parent reply other threads:[~2002-12-18 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200212181807.gBII7Wn28845@hera.kernel.org>
2002-12-18 18:21 ` ALSA update Greg KH
2002-12-18 19:17 ` Jaroslav Kysela
2002-12-18 19:27 ` Greg KH [this message]
2002-12-19 12:17 ` Takashi Iwai
2002-12-18 19:51 ` Ruslan U. Zakirov
2002-12-19 12:07 ` Takashi Iwai
2002-12-19 12:18 ` Jaroslav Kysela
2002-12-20 0:27 ` Greg KH
2002-12-19 23:04 ` Bill Davidsen
2002-11-10 20:44 Jaroslav Kysela
[not found] <Pine.NEB.4.44.0210151048240.20607-100000@mimas.fachschaften.tu-muenchen.de>
2002-10-15 9:55 ` Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 19:45 Jaroslav Kysela
2002-10-14 19:58 ` David S. Miller
2002-10-14 22:43 ` Jaroslav Kysela
2002-10-15 17:08 ` David S. Miller
2002-10-15 19:45 ` Jaroslav Kysela
2002-10-15 19:45 ` David S. Miller
2002-10-16 16:20 ` 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=20021218192740.GC32190@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox