public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [slave-dma:topic/dmaengine_dt 17/20] drivers/dma/dmaengine.c:65:26: fatal error: linux/of_dma.h: No
Date: Tue, 25 Sep 2012 11:37:03 +0000	[thread overview]
Message-ID: <20120925113703.GA5157@localhost> (raw)

Hi Vinod,

I noticed that kernel build failed on this commit and get fixed by
the next next commit. Do you want me to do commit-by-commit tests on
your tree, or test branch head first which will ignore such interim errors?

Thanks,
Fengguang
---

tree:   git://git.infradead.org/users/vkoul/slave-dma.git topic/dmaengine_dt
head:   be2e7726dc84371736996e05d10331f70afd50c1
commit: 528499a7037ebec0636d928f88cd783c618df3c5 [17/20] dmaengine: add helper function to request a slave DMA channel
config: x86_64-allmodconfig


All error/warnings:

drivers/dma/dmaengine.c:65:26: fatal error: linux/of_dma.h: No such file or directory
compilation terminated.

vim +65 drivers/dma/dmaengine.c
    59	#include <linux/rcupdate.h>
    60	#include <linux/mutex.h>
    61	#include <linux/jiffies.h>
    62	#include <linux/rculist.h>
    63	#include <linux/idr.h>
    64	#include <linux/slab.h>
  > 65	#include <linux/of_dma.h>
    66	
    67	static DEFINE_MUTEX(dma_list_mutex);
    68	static DEFINE_IDR(dma_idr);

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

             reply	other threads:[~2012-09-25 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 11:37 Fengguang Wu [this message]
2012-09-25 16:37 ` [slave-dma:topic/dmaengine_dt 17/20] drivers/dma/dmaengine.c:65:26: fatal error: linux/of_dma.h: Vinod Koul
2012-09-26  0:45 ` Fengguang Wu

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=20120925113703.GA5157@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.kernel.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