From: Fengguang Wu <fengguang.wu@intel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, kernel-janitors@vger.kernel.org
Subject: Re: [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM'
Date: Thu, 6 Sep 2012 11:18:01 +0800 [thread overview]
Message-ID: <20120906031801.GA16913@localhost> (raw)
In-Reply-To: <1346900756.19098.20.camel@pasglop>
On Thu, Sep 06, 2012 at 01:05:56PM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2012-09-06 at 11:03 +0800, Fengguang Wu wrote:
> >
> > No problem. Sorry I didn't know that. Will test HEAD commits only for
> > this branch in future.
>
> Actually, I'd rather you continue doing bisection tests, it's good, I
> can whack on the head of people who submit stuff with breakage.
OK.
> In fact, next time around, I'll try to be more pro-active at putting
> things in my rebase-able test branch so you get a chance to run your
> tests on it and we can find & fix these before it hits next. I'll let
> you know when I do it.
That would be great.
> In the meantime, maybe just blacklist those commits ?
Should not necessary if I understand you right. FYI the build system
will auto ignore all notified build errors and skip compiled commits.
Thanks,
Fengguang
prev parent reply other threads:[~2012-09-06 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 2:20 [powerpc:next 11/29] arch/powerpc/platforms/pseries/iommu.c:1064:2: error: implicit declaration of function 'memblock_end_of_DRAM' Fengguang Wu
2012-09-06 2:44 ` Benjamin Herrenschmidt
2012-09-06 2:49 ` Benjamin Herrenschmidt
2012-09-06 3:03 ` Fengguang Wu
2012-09-06 3:05 ` Benjamin Herrenschmidt
2012-09-06 3:18 ` 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=20120906031801.GA16913@localhost \
--to=fengguang.wu@intel.com \
--cc=benh@kernel.crashing.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).