All of lore.kernel.org
 help / color / mirror / Atom feed
From: cmedia <cltien@cmedia.com.tw>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux driver for c-media cm8x38 ver 4.12 released
Date: Mon, 27 Nov 2000 20:59:51 -0500	[thread overview]
Message-ID: <3A231197.A62DE01F@cmedia.com.tw> (raw)
In-Reply-To: <3A1C62AA.5D4579B3@cmedia.com.tw> <20001123033948.R2918@wire.cadcamlab.org> <3A1D1998.5A22EA7C@cmedia.com.tw> <14877.10577.518203.721355@wire.cadcamlab.org>

Hi,

I change it so a release 4.14 posted at
http://members.home.net/puresoft/cmedia.html. This version has no functional
change.

Sincerely,
ChenLi Tien

Peter Samuelson wrote:

> [ChenLi Tien]
> > > I don't think the (2,3,0) ifdef is necessary.  Just use the labeled
> > > initializers for all kernels.  See also cm_audio_fops, cm_dsp_fops,
> > > cm_midi_fops, cm_dmfm_fops.
> >
> > Yes, as 2.3.x series is not for end-user, I can remove them. I keep it for
> > easy to tell what's different for kernel 2.3 and 2.4.
>
> What I meant was, the code which you have '#if version >= 2.3.0' is
> also valid for 2.2.  You should not have any conditional code there
> except the 'owner:' member, which is '#if version >= 2.4.0'.
>
> > > No need for '#ifdef MODULE'.
> >
> > I will remove it if kernel 2.2 can work.
>
> It can.  I checked 2.2.0.
>
> Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-28  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-23  0:19 Linux driver for c-media cm8x38 ver 4.12 released cmedia
2000-11-23  9:39 ` Peter Samuelson
2000-11-23 13:20   ` cmedia
2000-11-23 14:27     ` Peter Samuelson
2000-11-28  1:59       ` cmedia [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=3A231197.A62DE01F@cmedia.com.tw \
    --to=cltien@cmedia.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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 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.