Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1211446

Re: linux-next: build failure after merge of the powerpc tree

From Michael Ellerman <mpe@ellerman.id.au>
Newsgroups linux.kernel
Subject Re: linux-next: build failure after merge of the powerpc tree
Date 2015-08-22 13:20 +0200
Message-ID <q0f05-tR-3@gated-at.bofh.it> (permalink)
References <pZPS1-6zf-7@gated-at.bofh.it> <pZQuL-7xY-15@gated-at.bofh.it> <q04el-1R3-1@gated-at.bofh.it> <q08rD-7ZZ-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Sat, 2015-08-22 at 09:39 +0530, Vasant Hegde wrote:
> On 08/22/2015 05:10 AM, Michael Ellerman wrote:
> > On Fri, 2015-08-21 at 14:29 +0530, Vasant Hegde wrote:
> >> On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> After merging the nvdimm tree, today's linux-next build (powerpc
> >>> allyesconfig) failed like this:
> >>
> >> Stephen,
> >>
> >> Thanks for reporting! I checked powerpc tree.. This is because of commit
> >> 8a8d9181 in powerpc tree.. Basically Michael missed one hunk (below hunk in
> >> opal-api.h)
> > 
> > Hmm, looks like it.
> > 
> > I do remember the patch didn't apply to my tree, so I guess I accidentally
> > dropped a hunk when I was forcing it to apply.
> 
> Hmmm yeah..My patchset was based on upstream tree (4.2-rc7) instead of powerpc
> next tree.

That's OK. Usually that works fine, and usually when there is a conflict I can
just fix it up. I'm not sure how I managed to drop that chunk, I'll have to go
back and look at what I did. I suspect I hand-edited the patch, and if you do
that wrong it can lead to patch just ignoring the rest of the patch.

I probably should have just asked you to rebase on my next, but given it was
already version 10 I didn't really feel like doing another revision :)

> > Also we're obviously not building this in any of our defconfigs. Can you please
> > send a patch to enable it for pseries_defconfig and ppc64_defconfig.
> 
> Sure.. Will send separate patch.

Thanks.

cheers


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

linux-next: build failure after merge of the powerpc tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-08-21 10:30 +0200
  Re: linux-next: build failure after merge of the powerpc tree Vasant Hegde <hegdevasant@linux.vnet.ibm.com> - 2015-08-21 11:10 +0200
    Re: linux-next: build failure after merge of the powerpc tree Michael Ellerman <mpe@ellerman.id.au> - 2015-08-22 01:50 +0200
      Re: linux-next: build failure after merge of the powerpc tree Vasant Hegde <hegdevasant@linux.vnet.ibm.com> - 2015-08-22 06:20 +0200
        Re: linux-next: build failure after merge of the powerpc tree Michael Ellerman <mpe@ellerman.id.au> - 2015-08-22 13:20 +0200

csiph-web