linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] update PCI quirks
Date: 07 Mar 2003 12:34:41 +0000	[thread overview]
Message-ID: <1047040481.20794.3.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.21.0303071150040.13981-100000@vervain.sonytel.be>

On Fri, 2003-03-07 at 10:50, Geert Uytterhoeven wrote:

> > + * we do now ? We don't want is pci_enable_device to come along
>                   ^^^^^^^^^^^^^^^^
> 		  What we don't want is?

Or just "We don't want". I guess I changed my mind half way through 8)
Thanks


      reply	other threads:[~2003-03-07 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200303070214.h272EH121792@hera.kernel.org>
2003-03-07 10:50 ` [PATCH] update PCI quirks Geert Uytterhoeven
2003-03-07 12:34   ` Alan Cox [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=1047040481.20794.3.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --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).