From: Balbir Singh <bsingharora@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: Balbir Singh <bsingharora@gmail.com>,
kbuild-all@01.org, mpe@ellerman.id.au, linuxppc-dev@ozlabs.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/3] powerpc/xmon: Apply binutils changes to upgrade disassembly
Date: Wed, 8 Feb 2017 16:25:20 +0530 [thread overview]
Message-ID: <20170208105520.GE17068@localhost.localdomain> (raw)
In-Reply-To: <201702021636.pHsYmBR1%fengguang.wu@intel.com>
On Thu, Feb 02, 2017 at 04:16:41PM +0800, kbuild test robot wrote:
> Hi Balbir,
>
> [auto build test ERROR on powerpc/next]
> [also build test ERROR on v4.10-rc6 next-20170201]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
FYI for everyone
This patch does not compile, its documented in the patchset
and breaks bisect. The organization of this patch is driven
more by licensing constraints and modularization
Balbir
next prev parent reply other threads:[~2017-02-08 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 5:03 [PATCH 0/3] Update xmon disassembly Balbir Singh
2017-02-02 5:03 ` [PATCH 1/3] powerpc/xmon Update ppc-dis/opc.c and ppc.h Balbir Singh
2017-02-02 8:44 ` kbuild test robot
2017-02-16 5:59 ` [1/3] " Michael Ellerman
2017-02-02 5:03 ` [PATCH 2/3] powerpc/xmon: Apply binutils changes to upgrade disassembly Balbir Singh
2017-02-02 8:16 ` kbuild test robot
2017-02-08 10:55 ` Balbir Singh [this message]
2017-02-08 11:27 ` Michael Ellerman
2017-02-02 5:03 ` [PATCH 3/3] powerpc/xmon: Enable disassembly files (compilation changes) Balbir Singh
2017-02-02 5:09 ` [PATCH 0/3] Update xmon disassembly Balbir Singh
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=20170208105520.GE17068@localhost.localdomain \
--to=bsingharora@gmail.com \
--cc=kbuild-all@01.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
--cc=paulmck@linux.vnet.ibm.com \
/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).