From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [PATCH] PCI update for 2.6.3
Date: Fri, 20 Feb 2004 11:06:22 -0800 [thread overview]
Message-ID: <10773039823749@kroah.com> (raw)
In-Reply-To: <10773039813517@kroah.com>
ChangeSet 1.1581, 2004/02/20 10:25:25-08:00, greg@kroah.com
[PATCH] PCI Hotplug: fix build warnings on 64 bit processors
drivers/pci/hotplug/cpqphp_sysfs.c | 4 ++--
drivers/pci/hotplug/pciehp_sysfs.c | 4 ++--
drivers/pci/hotplug/shpchp_sysfs.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff -Nru a/drivers/pci/hotplug/cpqphp_sysfs.c b/drivers/pci/hotplug/cpqphp_sysfs.c
--- a/drivers/pci/hotplug/cpqphp_sysfs.c Fri Feb 20 10:44:17 2004
+++ b/drivers/pci/hotplug/cpqphp_sysfs.c Fri Feb 20 10:44:17 2004
@@ -38,7 +38,7 @@
/* A few routines that create sysfs entries for the hot plug controller */
-static int show_ctrl (struct device *dev, char *buf)
+static ssize_t show_ctrl (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
@@ -82,7 +82,7 @@
}
static DEVICE_ATTR (ctrl, S_IRUGO, show_ctrl, NULL);
-static int show_dev (struct device *dev, char *buf)
+static ssize_t show_dev (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
diff -Nru a/drivers/pci/hotplug/pciehp_sysfs.c b/drivers/pci/hotplug/pciehp_sysfs.c
--- a/drivers/pci/hotplug/pciehp_sysfs.c Fri Feb 20 10:44:17 2004
+++ b/drivers/pci/hotplug/pciehp_sysfs.c Fri Feb 20 10:44:17 2004
@@ -38,7 +38,7 @@
/* A few routines that create sysfs entries for the hot plug controller */
-static int show_ctrl (struct device *dev, char *buf)
+static ssize_t show_ctrl (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
@@ -82,7 +82,7 @@
}
static DEVICE_ATTR (ctrl, S_IRUGO, show_ctrl, NULL);
-static int show_dev (struct device *dev, char *buf)
+static ssize_t show_dev (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
diff -Nru a/drivers/pci/hotplug/shpchp_sysfs.c b/drivers/pci/hotplug/shpchp_sysfs.c
--- a/drivers/pci/hotplug/shpchp_sysfs.c Fri Feb 20 10:44:17 2004
+++ b/drivers/pci/hotplug/shpchp_sysfs.c Fri Feb 20 10:44:17 2004
@@ -38,7 +38,7 @@
/* A few routines that create sysfs entries for the hot plug controller */
-static int show_ctrl (struct device *dev, char *buf)
+static ssize_t show_ctrl (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
@@ -82,7 +82,7 @@
}
static DEVICE_ATTR (ctrl, S_IRUGO, show_ctrl, NULL);
-static int show_dev (struct device *dev, char *buf)
+static ssize_t show_dev (struct device *dev, char *buf)
{
struct pci_dev *pci_dev;
struct controller *ctrl;
next prev parent reply other threads:[~2004-02-20 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10773039792482@kroah.com>
2004-02-20 19:06 ` [PATCH] PCI update for 2.6.3 Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH [this message]
2004-02-20 19:04 [BK PATCH] " Greg KH
2004-02-20 19:06 ` [PATCH] " Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:06 ` Greg KH
2004-02-20 19:19 ` Christoph Hellwig
2004-02-20 19:41 ` Dave Jones
2004-02-20 19:53 ` 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=10773039823749@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
/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