From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [slave-dma:topic/dmaengine_dt 17/20] drivers/dma/dmaengine.c:65:26: fatal error: linux/of_dma.h:
Date: Wed, 26 Sep 2012 00:45:15 +0000 [thread overview]
Message-ID: <20120926004515.GA5528@localhost> (raw)
In-Reply-To: <20120925113703.GA5157@localhost>
On Tue, Sep 25, 2012 at 09:55:13PM +0530, Vinod Koul wrote:
> On Tue, 2012-09-25 at 19:37 +0800, Fengguang Wu wrote:
> > 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?
> test branch head should be fine.
OK!
> But yes for kernel each patch needs to build on its own, this should not
> have happened in the first place.
Yeah, for that purpose ktest or aiaiai are good tools that's designed
to run such checks before pushing new commits. :-)
Thanks,
Fengguang
prev parent reply other threads:[~2012-09-26 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 11:37 [slave-dma:topic/dmaengine_dt 17/20] drivers/dma/dmaengine.c:65:26: fatal error: linux/of_dma.h: No Fengguang Wu
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 [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=20120926004515.GA5528@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;
as well as URLs for NNTP newsgroup(s).