public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>, "Ruslan U. Zakirov" <cubic@miee.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ALSA update
Date: Thu, 19 Dec 2002 16:27:33 -0800	[thread overview]
Message-ID: <20021220002732.GA9023@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212191314460.521-100000@pnote.perex-int.cz>

On Thu, Dec 19, 2002 at 01:18:10PM +0100, Jaroslav Kysela wrote:
> On Thu, 19 Dec 2002, Takashi Iwai wrote:
> 
> > At Wed, 18 Dec 2002 22:51:27 +0300 (MSK),
> > Ruslan U. Zakirov <cubic@miee.ru> wrote:
> > > 
> > > Hello, Jaroslav and All.
> > > How about other changes in new 2.5 kernel, like new PnP layer (Adam Belay)
> > > or changes with module & boot params (Rusty Russel)? There are now some
> > > changes in 2.5.52 kernel in sound/isa/opl3sa2.c that make this driver not
> > > compatible with other kernels. May be it's better split your tree in
> > > several trees for each version of kernels?
> > 
> > if possible, we'll build up some wrapper for 2.4 on alsa-driver (not
> > the codebase for 2.5) tree.  if not possible, yes, splitting to two
> > trees would be reasonable for such big changes...
> > 
> > thanks for noticing this issue.  i'll check them now.
> 
> I just removed the complete callback redefinitions from the 2.5 tree, 
> but we still have three small OLD_USB sections (mainly commenting 2.5 
> code which 2.4 code requires to override). Hopefully, it's quite reasonable.
> What do you think, Greg?

In the end, whatever is easiest for you do to, as I'm not the one who
has to maintain the code :)

That being said, the smaller the number of #ifdefs, the better.
Personally I would just have two different trees, but that's just me...

thanks,

greg k-h

  reply	other threads:[~2002-12-20  0: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
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 [this message]
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=20021220002732.GA9023@kroah.com \
    --to=greg@kroah.com \
    --cc=cubic@miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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