public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio•com>
To: ngupta@vflare•org
Cc: dan.magenheimer@oracle•com, gregkh@suse•de,
	devel@driverdev•osuosl.org, linux-kernel@vger•kernel.org,
	sfr@canb•auug.org.au, paul.gortmaker@windriver•com,
	linux-next@vger•kernel.org,
	Thadeu Lima de Souza Cascardo <cascardo@holoscopio•com>
Subject: [PATCH] zcache: include module.h for MODULE_LICENSE
Date: Wed,  3 Aug 2011 11:00:40 -0300	[thread overview]
Message-ID: <1312380040-28249-1-git-send-email-cascardo@holoscopio.com> (raw)
In-Reply-To: <20110803141641.00402b8e49dd68aa58c458ac@canb.auug.org.au>

The oncoming cleanup of module.h usage requires the explicit inclusion
of module.h when it was otherwise being included indirectly. Otherwise,
building zcache will fail.

Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio•com>
---
 drivers/staging/zcache/zcache-main.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/staging/zcache/zcache-main.c b/drivers/staging/zcache/zcache-main.c
index a58a03f..66469ac 100644
--- a/drivers/staging/zcache/zcache-main.c
+++ b/drivers/staging/zcache/zcache-main.c
@@ -19,6 +19,7 @@
  *   http://marc.info/?l=linux-mm&m=127811271605009
  */
 
+#include <linux/module.h>
 #include <linux/cpu.h>
 #include <linux/highmem.h>
 #include <linux/list.h>
-- 
1.7.5.4

  reply	other threads:[~2011-08-03 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03  4:16 linux-next: build failure after merge of the moduleh tree Stephen Rothwell
2011-08-03 14:00 ` Thadeu Lima de Souza Cascardo [this message]
2011-08-03 14:26   ` [PATCH] zcache: include module.h for MODULE_LICENSE Greg KH
2011-08-03 14:26 ` linux-next: build failure after merge of the moduleh tree 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=1312380040-28249-1-git-send-email-cascardo@holoscopio.com \
    --to=cascardo@holoscopio$(echo .)com \
    --cc=dan.magenheimer@oracle$(echo .)com \
    --cc=devel@driverdev$(echo .)osuosl.org \
    --cc=gregkh@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ngupta@vflare$(echo .)org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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