linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jdzheng@broadcom.com (Jiandong Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM/bcmring: missing sched.h inclusion in dma.c
Date: Tue, 3 Jan 2012 10:39:18 -0800	[thread overview]
Message-ID: <4F034B56.4060704@broadcom.com> (raw)

Add including of sched.h to fix build error.

This patch was submitted a couple of times last year but unfortunately 
got lost.

Signed-off-by: Jiandong Zheng <jdzheng@broadcom.com>
---
  arch/arm/mach-bcmring/dma.c |    1 +
  1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-bcmring/dma.c b/arch/arm/mach-bcmring/dma.c
index 0ca0005..ab109ff 100644
--- a/arch/arm/mach-bcmring/dma.c
+++ b/arch/arm/mach-bcmring/dma.c
@@ -24,6 +24,7 @@

  #include <linux/module.h>
  #include <linux/device.h>
+#include <linux/sched.h>
  #include <linux/dma-mapping.h>
  #include <linux/interrupt.h>
  #include <linux/irqreturn.h>
-- 
1.7.5.4

             reply	other threads:[~2012-01-03 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 18:39 Jiandong Zheng [this message]
2012-01-04 22:11 ` [PATCH] ARM/bcmring: missing sched.h inclusion in dma.c Olof Johansson

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=4F034B56.4060704@broadcom.com \
    --to=jdzheng@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).