All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: alan@lxorguk.ukuu.org.uk
Cc: adam@yggdrasil.com, mj@ucw.cz, axboe@suse.de,
	andre@linux-ide.org, toe@unlserve.unl.edu, kraxel@bytesex.org,
	linux-kernel@vger.kernel.org
Subject: Re: Patch(2.5.52): Add missing PCI ID's for nVidia IDE and PlanB frame grabber
Date: Thu, 19 Dec 2002 21:17:03 +0100 (CET)	[thread overview]
Message-ID: <E18P76a-00007a-00@piglet.grunz.lu> (raw)
In-Reply-To: <1040259741.26882.0.camel@irongate.swansea.linux.org.uk>

On  19 Dec, this message from Alan Cox echoed through cyberspace:
> On Wed, 2002-12-18 at 23:35, Adam J. Richter wrote:
>> Hi Martin,
>> 
>> 	This patch adds two pci device id definitions needed to make
>> a couple of drivers compile in 2.5.52:
>> 
>> 	drivers/ide/pci/nvidia.c needs PCI_DEVICE_IDE_NVIDIA_NFORCE_IDE
>> 	drivers/media/video/planb.c needs PCI_DEVICE_IDE_APPLE_PLANB
>> 
>> 	If nobody complains, could you please forward these changes to
>> Linus and confirm to me that you have done this (so I can have a
>> better idea of what to do if they not appear in 2.5.53)?  Thanks in
>> advance.
> 
> The NVIDIA one is right, someoen removed it from Linus tree by accident
> in 2.5.51 or so when adding other Nvidia bits.

The PLANB one is right as well; it probably never was in there, but is
indeed useful to the driver.

Cheers

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


      reply	other threads:[~2002-12-19 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18 23:35 Patch(2.5.52): Add missing PCI ID's for nVidia IDE and PlanB frame grabber Adam J. Richter
2002-12-19  1:02 ` Alan Cox
2002-12-19 20:17   ` Michel Lanners [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=E18P76a-00007a-00@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=toe@unlserve.unl.edu \
    /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.