All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: Marcelo Tosatti
	<mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	"kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org list"
	<kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] PPC: KVM: Book E doesn't have __end_interrupts.
Date: Tue, 19 Oct 2010 15:33:12 +0000	[thread overview]
Message-ID: <4CBDBA38.5030603@redhat.com> (raw)
In-Reply-To: <1C5182C8-B875-44B9-BBDF-104B68211F06-l3A5Bk7waGM@public.gmane.org>

  On 10/19/2010 05:26 PM, Alexander Graf wrote:
>
>> 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@kernel.org.
>>
>> Ah, there is no need to backport it, the code is not in linux-2.6.git.
> It didn't make it there yet? Interesting. Seems like pretty long delays between kvm.git and linux-2.6.git then. That code is months old :). That makes this matter a lot easier though. Thanks for checking before I emberass myself :).
>

Patches merged to kvm.git await the next merge window, so up to a three 
months delay.  Security and recent regression fixes go straight in.


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: Marcelo Tosatti
	<mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	"kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org list"
	<kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] PPC: KVM: Book E doesn't have __end_interrupts.
Date: Tue, 19 Oct 2010 17:33:12 +0200	[thread overview]
Message-ID: <4CBDBA38.5030603@redhat.com> (raw)
In-Reply-To: <1C5182C8-B875-44B9-BBDF-104B68211F06-l3A5Bk7waGM@public.gmane.org>

  On 10/19/2010 05:26 PM, Alexander Graf wrote:
>
>> 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.
> It didn't make it there yet? Interesting. Seems like pretty long delays between kvm.git and linux-2.6.git then. That code is months old :). That makes this matter a lot easier though. Thanks for checking before I emberass myself :).
>

Patches merged to kvm.git await the next merge window, so up to a three 
months delay.  Security and recent regression fixes go straight in.

  parent reply	other threads:[~2010-10-19 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 22:35 [PATCH] PPC: KVM: Book E doesn't have __end_interrupts Scott Wood
     [not found] ` <20101018223548.GA31033-N/eSCTBpGwP7j4BuCOFQISmX4OfbXNuMKnGXBo5VDl8@public.gmane.org>
2010-10-18 22:57   ` Alexander Graf
2010-10-18 22:57     ` Alexander Graf
     [not found]     ` <63D9E9B6-3FF4-4A13-A087-0B509208F12A-l3A5Bk7waGM@public.gmane.org>
2010-10-19 14:06       ` Marcelo Tosatti
2010-10-19 14:06         ` Marcelo Tosatti
     [not found]         ` <20101019140657.GA4833-I4X2Mt4zSy4@public.gmane.org>
2010-10-19 15:26           ` Alexander Graf
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 [this message]
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=4CBDBA38.5030603@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf-l3A5Bk7waGM@public.gmane.org \
    --cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtosatti-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.