linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@ufl.edu>
To: Daniel Bertrand <d.bertrand@ieee.ca>
Cc: Dylan Griffiths <Dylan_G@bigfoot.com>,
	emu10k1-devel <emu10k1-devel@opensource.creative.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Emu10k1-devel] Re: Buggy emu10k1 drivers.
Date: 17 Jun 2001 20:33:25 -0400	[thread overview]
Message-ID: <992824408.3203.7.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0106171707150.2262-100000@kilrogg>
In-Reply-To: <Pine.LNX.4.33.0106171707150.2262-100000@kilrogg>

On 17 Jun 2001 17:25:11 -0700, Daniel Bertrand wrote:
> On 17 Jun 2001, Robert Love wrote:
> > if the driver in the kernel is that old, could we try merging a newer
> > release?  is there any reason why it has not been done yet?
> 
> A patch was submitted to Alan in April but appears to have never made it
> in, I'm not sure what his reason was.

can a patch against the latest 2.4-ac be resubmitted to the list and
alan?  if it again does not get merged, i will take a look at it and
find what political problems it has.  i use the emu10k1 and would like
the updated driver.

-- 
Robert M. Love
rml@ufl.edu
rml@tech9.net


  reply	other threads:[~2001-06-18  0:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 10:52 Buggy emu10k1 drivers Dylan Griffiths
2001-06-17 22:17 ` [Emu10k1-devel] " Daniel Bertrand
2001-06-18  0:00   ` Robert Love
2001-06-18  0:25     ` Daniel Bertrand
2001-06-18  0:33       ` Robert Love [this message]
2001-06-18  2:22       ` Joseph Carter
2001-06-19 22:57     ` Dylan Griffiths
2001-06-18  0:01   ` Nerijus Baliunas

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=992824408.3203.7.camel@phantasy \
    --to=rml@ufl.edu \
    --cc=Dylan_G@bigfoot.com \
    --cc=d.bertrand@ieee.ca \
    --cc=emu10k1-devel@opensource.creative.com \
    --cc=linux-kernel@vger.kernel.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 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).