linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: powerpc: book3s: Fix build break for BOOK3S_32
Date: Sat, 5 Oct 2013 09:45:09 +1000	[thread overview]
Message-ID: <20131004234509.GB2256@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1945837D-825F-4509-9D7C-D839917863A9@suse.de>

On Fri, Oct 04, 2013 at 03:00:11PM +0200, Alexander Graf wrote:
> 
> On 04.10.2013, at 14:35, Paul Mackerras wrote:
> 
> > On Fri, Oct 04, 2013 at 02:27:02PM +0200, Alexander Graf wrote:
> >> 
> >> On 04.10.2013, at 14:23, Alexander Graf wrote:
> >> 
> >>> 
> >>> On 03.10.2013, at 06:14, Paul Mackerras wrote:
> >>> 
> >>>> On Wed, Oct 02, 2013 at 08:08:44PM +0530, Aneesh Kumar K.V wrote:
> >>>>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> >>>>> 
> >>>>> This was introduced by 85a0d845d8bb5df5d2669416212f56cbe1474c6b
> >>>> 
> >>>> It's a good idea to give the headline of the commit as well as the ID.
> >>>> I also like to trim the ID to 10 characters or so.  So it should look
> >>>> like this:
> >>>> 
> >>>> This was introduced by 85a0d845d8 ("KVM: PPC: Book3S PR: Allocate
> >>>> kvm_vcpu structs from kvm_vcpu_cache").
> >>>> 
> >>>>> arch/powerpc/kvm/book3s_pr.c: In function 'kvmppc_core_vcpu_create':
> >>>>> arch/powerpc/kvm/book3s_pr.c:1182:30: error: 'struct kvmppc_vcpu_book3s' has no member named 'shadow_vcpu'
> >>>>> make[1]: *** [arch/powerpc/kvm/book3s_pr.o] Error 1
> >>>>> 
> >>>>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> >>>> 
> >>>> Acked-by: Paul Mackerras <paulus@samba.org>
> >>> 
> >>> Would you guys mind if I merge this into the offending patch? It's not trickled into -next yet, so rebasing should work.
> >>> 
> >>> If not, please resend with the fixed commit message.
> >> 
> >> Eh - I must've missed v2 :). So that leaves only the question on whether you'd be ok to squash the patch instead. It'd help bisectability.
> > 
> > I'm OK with that.  If you do, why don't you squash the first of the
> > two patches that I just sent into the commit it fixes as well?
> 
> Because patch 1/2 spans two separate commits it would have to get squashed into (6aa82e, 70afec) and patch 2/2 doesn't make sense to get squashed anywhere :).

Actually 70afec is fine, if you look at it, it's only 6aa82e that
needs fixing.

Paul.

  reply	other threads:[~2013-10-04 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 14:38 [PATCH] kvm: powerpc: book3s: Fix build break for BOOK3S_32 Aneesh Kumar K.V
2013-10-03  4:14 ` Paul Mackerras
2013-10-04 12:23   ` Alexander Graf
2013-10-04 12:27     ` Alexander Graf
2013-10-04 12:35       ` Paul Mackerras
2013-10-04 13:00         ` Alexander Graf
2013-10-04 23:45           ` Paul Mackerras [this message]
2013-10-04 23:59             ` Alexander Graf
2013-10-04 14:24       ` Aneesh Kumar K.V

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=20131004234509.GB2256@iris.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=agraf@suse.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@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).