From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [slave-dma:next 10/44] arch/arm/mach-spear13xx/spear1310.c:50:2: error: 'DMAC0_BASE' undeclared here (not in a function)
Date: Sun, 6 Jan 2013 20:31:52 -0800 [thread overview]
Message-ID: <20130107043152.GA2140@intel.com> (raw)
In-Reply-To: <CAKohpo=Z2Y1Vo3T4x3y__Xp_dKETtO-MCQDHhRYNwJ5-YztgVw@mail.gmail.com>
On Mon, Jan 07, 2013 at 10:09:53AM +0530, Viresh Kumar wrote:
> Hi Vinod,
>
> On 6 January 2013 23:52, kbuild test robot <fengguang.wu@intel.com> wrote:
> > tree: git://git.infradead.org/users/vkoul/slave-dma.git next
> > head: 3c1eea5112859d9467a27d4f6671cb3162481420
> > commit: 9a1e6fbf2b084ff903d33671b3f7fb09cd633f78 [10/44] ARM: SPEAr13xx: Pass DW DMAC platform data from DT
> > config: make ARCH=arm spear13xx_defconfig
> >
> > All error/warnings:
> >
> > FATAL ERROR: Unable to parse input tree
> > --
> > arch/arm/mach-spear13xx/spear1310.c:50:2: error: 'DMAC0_BASE' undeclared here (not in a function)
> > arch/arm/mach-spear13xx/spear1310.c:51:2: error: 'DMAC1_BASE' undeclared here (not in a function)
>
> There were multiple issues with the latest rebase done on 3.8-rc2.
> Over that there is an issue in
> this patch, due to which merge with ARM-SoC tree was broken... I have
> fixed rebase
> and merge issues in below patch. Please pick it up:
>
> (ARM mail servers are facing some issues now a days and so patch would
> be broken,
> hence attaching it too)
Thanks for this. Yes rebase seems to have caused many issues so I am redoing it
right now. Will let you know once the tree is updated
--
~Vinod
prev parent reply other threads:[~2013-01-07 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50e9c0da.1vFAsky7xkvAf1HF%fengguang.wu@intel.com>
2013-01-07 4:39 ` [slave-dma:next 10/44] arch/arm/mach-spear13xx/spear1310.c:50:2: error: 'DMAC0_BASE' undeclared here (not in a function) Viresh Kumar
2013-01-07 4:31 ` Vinod Koul [this message]
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=20130107043152.GA2140@intel.com \
--to=vinod.koul@intel.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 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.