From: Marcelo Tosatti <mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org list"
<kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] PPC: KVM: Book E doesn't have __end_interrupts.
Date: Tue, 19 Oct 2010 12:06:57 -0200 [thread overview]
Message-ID: <20101019140657.GA4833@amt.cnet> (raw)
In-Reply-To: <63D9E9B6-3FF4-4A13-A087-0B509208F12A-l3A5Bk7waGM@public.gmane.org>
On Tue, Oct 19, 2010 at 12:57:29AM +0200, Alexander Graf wrote:
>
> On 19.10.2010, at 00:35, Scott Wood wrote:
>
> > Fix an unresolved symbol with CONFIG_KVM_GUEST plus CONFIG_RELOCATABLE on
> > Book E.
>
> Thanks, applied to the kvm-ppc-next tree.
>
> Avi, could you please pull my tree asap? That breakage is pretty bad
> and all my fault :(.
Done.
> It might be good if we could have a stable update
> for that particular patch as well. Should I add a stable tag in the
> patch description for that?
Please do it yourself (active trees are 2.6.35 and 2.6.32), since we
have no way to test it. Wait for it to be merged in linux-2.6.git,
then send the patch (specifying which kernel it applies to) to
stable-DgEjT+Ai2yi4UlQgPVntAg@public.gmane.org
Ah, there is no need to backport it, the code is not in linux-2.6.git.
next prev parent reply other threads:[~2010-10-19 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101018223548.GA31033@udp111988uds.am.freescale.net>
[not found] ` <20101018223548.GA31033-N/eSCTBpGwP7j4BuCOFQISmX4OfbXNuMKnGXBo5VDl8@public.gmane.org>
2010-10-18 22:57 ` [PATCH] PPC: KVM: Book E doesn't have __end_interrupts Alexander Graf
[not found] ` <63D9E9B6-3FF4-4A13-A087-0B509208F12A-l3A5Bk7waGM@public.gmane.org>
2010-10-19 14:06 ` Marcelo Tosatti [this message]
[not found] ` <20101019140657.GA4833-I4X2Mt4zSy4@public.gmane.org>
2010-10-19 15:26 ` Alexander Graf
[not found] ` <1C5182C8-B875-44B9-BBDF-104B68211F06-l3A5Bk7waGM@public.gmane.org>
2010-10-19 15:33 ` Avi Kivity
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=20101019140657.GA4833@amt.cnet \
--to=mtosatti-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=agraf-l3A5Bk7waGM@public.gmane.org \
--cc=avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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