linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Balram Adlakha <b_adlakha@softhome.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2 OSS emu10k1
Date: 27 Jul 2003 21:39:39 +0100	[thread overview]
Message-ID: <1059338379.13871.0.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030727190257.GA2840@localhost.localdomain>

On Sul, 2003-07-27 at 20:02, Balram Adlakha wrote:
> I cannot compile the emu10k1 module:
> 
> sound/oss/emu10k1/hwaccess.c:182: redefinition of `emu10k1_writefn0_2'
> sound/oss/emu10k1/hwaccess.c:164: `emu10k1_writefn0_2' previously defined here

Looks like bad patching 182 is unrelated in my tree


  parent reply	other threads:[~2003-07-28  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 19:02 Balram Adlakha
2003-07-27 19:14 ` Alistair J Strachan
2003-07-27 20:39 ` Alan Cox [this message]
2003-07-27 23:35 ` Rudo Thomas
2003-07-28 20:41 ` Randy.Dunlap

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=1059338379.13871.0.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=b_adlakha@softhome.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-test2 OSS emu10k1' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).