From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Update for 2.6.2-rc2
Date: Thu, 29 Jan 2004 17:31:46 -0800 [thread overview]
Message-ID: <1075426306325@kroah.com> (raw)
In-Reply-To: <10754263054147@kroah.com>
ChangeSet 1.1510, 2004/01/29 14:26:28-08:00, eike-hotplug@sf-tec.de
[PATCH] PCI Hotplug: Fixup pcihp_skeleton.c
The functions are not named *_skel_*, so it seems useful not to call them with
this.
drivers/pci/hotplug/pcihp_skeleton.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -Nru a/drivers/pci/hotplug/pcihp_skeleton.c b/drivers/pci/hotplug/pcihp_skeleton.c
--- a/drivers/pci/hotplug/pcihp_skeleton.c Thu Jan 29 17:24:44 2004
+++ b/drivers/pci/hotplug/pcihp_skeleton.c Thu Jan 29 17:24:44 2004
@@ -370,10 +370,10 @@
* Initilize the slot info structure with some known
* good values.
*/
- info->power_status = get_skel_power_status(slot);
- info->attention_status = get_skel_attention_status(slot);
- info->latch_status = get_skel_latch_status(slot);
- info->adapter_status = get_skel_adapter_status(slot);
+ info->power_status = get_power_status(slot);
+ info->attention_status = get_attention_status(slot);
+ info->latch_status = get_latch_status(slot);
+ info->adapter_status = get_adapter_status(slot);
dbg ("registering slot %d\n", i);
retval = pci_hp_register (slot->hotplug_slot);
next prev parent reply other threads:[~2004-01-30 1:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 1:29 [BK PATCH] PCI update for 2.6.2-rc2 Greg KH
2004-01-30 1:31 ` [PATCH] PCI Update " Greg KH
2004-01-30 1:31 ` Greg KH [this message]
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 12:26 ` Russell King
2004-01-31 0:23 ` Greg KH
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=1075426306325@kroah.com \
--to=greg@kroah.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