From: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mike Marciniszyn
<infinipath-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: [PATCH -next] infiniband: fix ipath_chip_init.c build errors
Date: Fri, 07 Oct 2011 13:59:41 -0700 [thread overview]
Message-ID: <4E8F683D.9020604@xenotime.net> (raw)
In-Reply-To: <20111007174230.702f4a0bf1fe71dab5e10961-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
From: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Add <linux/stat.h> to fix build errors:
drivers/infiniband/hw/ipath/ipath_init_chip.c:54:1: error: 'S_IRUGO' undeclared here (not in a function)
drivers/infiniband/hw/ipath/ipath_init_chip.c:54:1: error: bit-field '<anonymous>' width not an integer constant
drivers/infiniband/hw/ipath/ipath_init_chip.c:67:1: error: 'S_IWUSR' undeclared here (not in a function)
drivers/infiniband/hw/ipath/ipath_init_chip.c:67:1: error: bit-field '<anonymous>' width not an integer constant
Signed-off-by: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: Mike Marciniszyn <infinipath-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
---
drivers/infiniband/hw/ipath/ipath_init_chip.c | 1 +
1 file changed, 1 insertion(+)
--- next-2011-1007.orig/drivers/infiniband/hw/ipath/ipath_init_chip.c
+++ next-2011-1007/drivers/infiniband/hw/ipath/ipath_init_chip.c
@@ -35,6 +35,7 @@
#include <linux/netdevice.h>
#include <linux/moduleparam.h>
#include <linux/slab.h>
+#include <linux/stat.h>
#include <linux/vmalloc.h>
#include "ipath_kernel.h"
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Marciniszyn <infinipath@qlogic.com>,
linux-rdma@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH -next] infiniband: fix ipath_chip_init.c build errors
Date: Fri, 07 Oct 2011 13:59:41 -0700 [thread overview]
Message-ID: <4E8F683D.9020604@xenotime.net> (raw)
In-Reply-To: <20111007174230.702f4a0bf1fe71dab5e10961@canb.auug.org.au>
From: Randy Dunlap <rdunlap@xenotime.net>
Add <linux/stat.h> to fix build errors:
drivers/infiniband/hw/ipath/ipath_init_chip.c:54:1: error: 'S_IRUGO' undeclared here (not in a function)
drivers/infiniband/hw/ipath/ipath_init_chip.c:54:1: error: bit-field '<anonymous>' width not an integer constant
drivers/infiniband/hw/ipath/ipath_init_chip.c:67:1: error: 'S_IWUSR' undeclared here (not in a function)
drivers/infiniband/hw/ipath/ipath_init_chip.c:67:1: error: bit-field '<anonymous>' width not an integer constant
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc: Mike Marciniszyn <infinipath@qlogic.com>
Cc: linux-rdma@vger.kernel.org
---
drivers/infiniband/hw/ipath/ipath_init_chip.c | 1 +
1 file changed, 1 insertion(+)
--- next-2011-1007.orig/drivers/infiniband/hw/ipath/ipath_init_chip.c
+++ next-2011-1007/drivers/infiniband/hw/ipath/ipath_init_chip.c
@@ -35,6 +35,7 @@
#include <linux/netdevice.h>
#include <linux/moduleparam.h>
#include <linux/slab.h>
+#include <linux/stat.h>
#include <linux/vmalloc.h>
#include "ipath_kernel.h"
next prev parent reply other threads:[~2011-10-07 20:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 6:42 linux-next: Tree for Oct 7 Stephen Rothwell
[not found] ` <20111007174230.702f4a0bf1fe71dab5e10961-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-10-07 20:57 ` [PATCH -next] usb gadget: fix langwell_udc.c build error Randy Dunlap
2011-10-07 20:57 ` Randy Dunlap
2011-10-08 10:03 ` Felipe Balbi
2011-10-09 17:50 ` Randy Dunlap
2011-10-09 22:36 ` Felipe Balbi
2011-10-09 23:05 ` Randy Dunlap
[not found] ` <4E9228CA.1060904-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-10-10 5:10 ` Felipe Balbi
2011-10-10 5:10 ` Felipe Balbi
2011-10-10 17:16 ` Greg KH
2011-10-10 17:40 ` Randy Dunlap
2011-10-09 23:33 ` Stephen Rothwell
2011-10-07 20:59 ` Randy Dunlap [this message]
2011-10-07 20:59 ` [PATCH -next] infiniband: fix ipath_chip_init.c build errors Randy Dunlap
[not found] ` <4E8F683D.9020604-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-10-07 21:21 ` Roland Dreier
2011-10-07 21:21 ` Roland Dreier
2011-10-07 22:05 ` Randy Dunlap
[not found] ` <4E8F77B8.3000805-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-10-07 23:28 ` Stephen Rothwell
2011-10-07 23:28 ` Stephen Rothwell
2011-10-10 19:02 ` Roland Dreier
2011-10-11 0:33 ` Stephen Rothwell
2011-10-10 18:57 ` Mike Marciniszyn
2011-10-10 19:02 ` Randy Dunlap
2011-10-11 13:06 ` Mike Marciniszyn
2011-10-11 13:06 ` Mike Marciniszyn
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=4E8F683D.9020604@xenotime.net \
--to=rdunlap-/uha2rfvqtnk1umjsbkqmq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=infinipath-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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.