From: Jeff Garzik <jgarzik@pobox.com>
To: Greg K-H <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
acurrid@nvidia.com
Subject: Re: [PATCH] PCI: amd74xx patch for new NVIDIA device IDs
Date: Wed, 01 Jun 2005 03:32:15 -0400 [thread overview]
Message-ID: <429D647F.5020701@pobox.com> (raw)
In-Reply-To: <111760252426@kroah.com>
Greg KH wrote:
> [PATCH] PCI: amd74xx patch for new NVIDIA device IDs
>
> Here's the 2.6 amd74xx patch for NVIDIA MCP51.
>
> Signed-off-by: Andy Currid <acurrid@nvidia.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
> commit af00f9811e0ccbd3db84ddc4cffb0da942653393
> tree 5a9c3b7f7d61d96d3624ad130b173a761cb7dac2
> parent 2ac2610b26c9da72820443328ff2c56c7b8c87b8
> author Andy Currid <acurrid@nvidia.com> Mon, 23 May 2005 08:55:45 -0700
> committer Greg KH <gregkh@suse.de> Tue, 31 May 2005 14:26:38 -0700
>
> drivers/ide/pci/amd74xx.c | 3 +++
> include/linux/pci_ids.h | 6 ++++++
This is hardly a PCI patch.
Has Bart, the IDE maintainer, acked this?
Jeff
next prev parent reply other threads:[~2005-06-01 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 5:08 [GIT PATCH] PCI bugfixes for 2.6.12-rc5 Greg KH
2005-06-01 5:08 ` [PATCH] PCI Hotplug: SHPCHP driver doesn't enable PERR and SERR properly Greg KH
2005-06-01 5:08 ` [PATCH] PCI Hotplug: shpchp driver doesn't program _HPP values properly Greg KH
2005-06-01 5:08 ` [PATCH] PCI: amd74xx patch for new NVIDIA device IDs Greg KH
2005-06-01 5:08 ` [PATCH] PCI Hotplug: more CPCI updates Greg KH
2005-06-02 2:41 ` Prarit Bhargava
2005-06-02 2:46 ` Prarit Bhargava
2005-06-02 3:03 ` Scott Murray
2005-06-06 19:48 ` Scott Murray
2005-06-01 7:32 ` Jeff Garzik [this message]
2005-06-01 9:50 ` [PATCH] PCI: amd74xx patch for new NVIDIA device IDs Bartlomiej Zolnierkiewicz
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=429D647F.5020701@pobox.com \
--to=jgarzik@pobox.com \
--cc=acurrid@nvidia.com \
--cc=greg@kroah.com \
--cc=linux-ide@vger.kernel.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 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.