public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Anand Gadiyar <gadiyar@ti•com>
To: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Cc: Anand Gadiyar <gadiyar@ti•com>,
	Paul Gortmaker <paul.gortmaker@windriver•com>,
	Samuel Ortiz <sameo@linux•intel.com>
Subject: [PATCH linux-next] mfd: omap-usb-host: add module.h and export.h to fix build break
Date: Fri, 19 Aug 2011 20:54:05 +0530	[thread overview]
Message-ID: <1313767445-20033-1-git-send-email-gadiyar@ti.com> (raw)

linux-next as of 20110817 fails to build if these two headers
are not included. Including module.h is sufficient for now,
but add export.h for EXPORT_SYMBOL and THIS_MODULE in advance
to avoid a later build break.

Signed-off-by: Anand Gadiyar <gadiyar@ti•com>
Cc: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: Samuel Ortiz <sameo@linux•intel.com>
---
Noticed this while testing another patch. I see similar
changes to other files in drivers/mfd made by Paul recently.

 drivers/mfd/omap-usb-host.c |    2 ++
 1 file changed, 2 insertions(+)

Index: linux-2.6/drivers/mfd/omap-usb-host.c
===================================================================
--- linux-2.6.orig/drivers/mfd/omap-usb-host.c
+++ linux-2.6/drivers/mfd/omap-usb-host.c
@@ -20,6 +20,8 @@
 #include <linux/types.h>
 #include <linux/slab.h>
 #include <linux/delay.h>
+#include <linux/export.h>
+#include <linux/module.h>
 #include <linux/platform_device.h>
 #include <linux/clk.h>
 #include <linux/dma-mapping.h>

             reply	other threads:[~2011-08-19 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 15:24 Anand Gadiyar [this message]
2011-08-19 15:48 ` [PATCH linux-next] mfd: omap-usb-host: add module.h and export.h to fix build break Paul Gortmaker
2011-08-22 15:06 ` Samuel Ortiz

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=1313767445-20033-1-git-send-email-gadiyar@ti.com \
    --to=gadiyar@ti$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    --cc=sameo@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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