All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: linux-mips@oss.sgi.com
Subject: Re: [RFC][PATCH]
Date: Sun, 30 Jun 2002 14:42:38 +0200	[thread overview]
Message-ID: <20020630144238.A342@dea.linux-mips.net> (raw)
In-Reply-To: <20020629184128.GX17216@lug-owl.de>; from jbglaw@lug-owl.de on Sat, Jun 29, 2002 at 08:41:29PM +0200

On Sat, Jun 29, 2002 at 08:41:29PM +0200, Jan-Benedict Glaw wrote:

> Please give me a comment on this patch. I'm currently tryin' to make the
> HAL2 driver work (yes, I've got my Indy out of the edge again and I'm
> going to use it as my desktop machine).
> 
> It fixes a compilation problem on dmabuf.c. There, DMA_AUTOINIT isn't
> defined. As ./include/asm-mips/dma.h looks like the asm-i386 file in
> general, I've copied the #define from the i386 port (and reformated the
> passus...).
> 
> If you think it'o okay, please apply it (and drop me a note:-p)

Sort of the right thing - why the heck does the Indy sound code have to
rely on code for the that antique PC DMA controller ...

  Ralf

  reply	other threads:[~2002-06-30 12:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 18:41 [RFC][PATCH] Jan-Benedict Glaw
2002-06-30 12:42 ` Ralf Baechle [this message]
2002-06-30 13:20   ` [RFC][PATCH] Jan-Benedict Glaw
2002-06-30 21:37     ` [RFC][PATCH] Ladislav Michl
  -- strict thread matches above, loose matches on Subject: below --
2006-02-16 15:19 [RFC] [PATCH] Darrel Goeddel
2006-02-16 18:12 ` Stephen Smalley
2006-02-16 20:09   ` Darrel Goeddel
2006-02-16 20:36     ` Stephen Smalley
2006-02-17 14:43       ` Darrel Goeddel
     [not found]         ` <1140192267.3083.119.camel@kirkland1.austin.ibm.com>
2006-02-17 16:23           ` Darrel Goeddel
2006-02-17 18:26           ` Stephen Smalley
2013-02-28  9:38 [RFC][PATCH] Oliver Schinagl

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=20020630144238.A342@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    /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.