From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org,
"kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PULL 0/7] ppc patch queue 2013-03-22
Date: Mon, 25 Mar 2013 22:54:03 +0000 [thread overview]
Message-ID: <1364252043.26945.19@snotra> (raw)
In-Reply-To: <AE7AB988-30BD-4462-A8F9-B141000F791F@suse.de> (from agraf@suse.de on Mon Mar 25 17:32:11 2013)
On 03/25/2013 05:32:11 PM, Alexander Graf wrote:
>
> On 25.03.2013, at 23:21, Scott Wood wrote:
>
> > -next? These are bugfixes, at least partially for regressions from
> 3.8 (that I pointed out before the bugs were merged!), that should go
> into master.
> >
> > Also, what about:
> > http://patchwork.ozlabs.org/patch/226227/
> >
> > You've got all four patches in kvm-ppc-3.9 as of a few weeks ago --
> will you be requesting a pull for that soon?
>
> Sigh. I guess I've screwed up the whole "let's make -next an unusable
> tree and fix regressions in a separate one" workflow again. Sorry for
> that.
>
> Since the patches already trickled into kvm's next branch, all we can
> do now is to wait for them to come back through stable, right?
> Marcelo, Gleb?
Well, you can still submit that kvm-ppc-3.9 pull request. :-)
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PULL 0/7] ppc patch queue 2013-03-22
Date: Mon, 25 Mar 2013 17:54:03 -0500 [thread overview]
Message-ID: <1364252043.26945.19@snotra> (raw)
In-Reply-To: <AE7AB988-30BD-4462-A8F9-B141000F791F@suse.de> (from agraf@suse.de on Mon Mar 25 17:32:11 2013)
On 03/25/2013 05:32:11 PM, Alexander Graf wrote:
>
> On 25.03.2013, at 23:21, Scott Wood wrote:
>
> > -next? These are bugfixes, at least partially for regressions from
> 3.8 (that I pointed out before the bugs were merged!), that should go
> into master.
> >
> > Also, what about:
> > http://patchwork.ozlabs.org/patch/226227/
> >
> > You've got all four patches in kvm-ppc-3.9 as of a few weeks ago --
> will you be requesting a pull for that soon?
>
> Sigh. I guess I've screwed up the whole "let's make -next an unusable
> tree and fix regressions in a separate one" workflow again. Sorry for
> that.
>
> Since the patches already trickled into kvm's next branch, all we can
> do now is to wait for them to come back through stable, right?
> Marcelo, Gleb?
Well, you can still submit that kvm-ppc-3.9 pull request. :-)
-Scott
next prev parent reply other threads:[~2013-03-25 22:54 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 14:25 [PULL 0/7] ppc patch queue 2013-03-22 Alexander Graf
2013-03-22 14:25 ` Alexander Graf
2013-03-22 14:25 ` [PATCH 1/7] KVM: PPC: move tsr update in a separate function Alexander Graf
2013-03-22 14:25 ` Alexander Graf
2013-03-22 14:25 ` [PATCH 2/7] KVM: PPC: Added one_reg interface for timer registers Alexander Graf
2013-03-22 14:25 ` Alexander Graf
2013-03-22 14:25 ` [PATCH 3/7] KVM: PPC: booke: Added debug handler Alexander Graf
2013-03-22 14:25 ` Alexander Graf
2013-03-22 14:26 ` [PATCH 4/7] kvm/ppc/e500: h2g_tlb1_rmap: esel 0 is valid Alexander Graf
2013-03-22 14:26 ` Alexander Graf
2013-03-22 14:26 ` [PATCH 5/7] kvm/ppc/e500: g2h_tlb1_map: clear old bit before setting new bit Alexander Graf
2013-03-22 14:26 ` Alexander Graf
2013-03-22 14:26 ` [PATCH 6/7] kvm/ppc/e500: eliminate tlb_refs Alexander Graf
2013-03-22 14:26 ` Alexander Graf
2013-03-22 14:26 ` [PATCH 7/7] KVM: PPC: Remove unused argument to kvmppc_core_dequeue_external Alexander Graf
2013-03-22 14:26 ` Alexander Graf
2013-03-24 9:45 ` [PULL 0/7] ppc patch queue 2013-03-22 Gleb Natapov
2013-03-24 9:45 ` Gleb Natapov
2013-03-25 22:21 ` Scott Wood
2013-03-25 22:21 ` Scott Wood
2013-03-25 22:32 ` Alexander Graf
2013-03-25 22:32 ` Alexander Graf
2013-03-25 22:54 ` Scott Wood [this message]
2013-03-25 22:54 ` Scott Wood
2013-03-25 22:59 ` Alexander Graf
2013-03-25 22:59 ` Alexander Graf
2013-03-25 23:16 ` Scott Wood
2013-03-25 23:16 ` Scott Wood
2013-03-25 23:35 ` Alexander Graf
2013-03-25 23:35 ` Alexander Graf
2013-03-26 1:33 ` Gleb Natapov
2013-03-26 1:33 ` Gleb Natapov
2013-03-26 1:59 ` Paul Mackerras
2013-03-26 1:59 ` Paul Mackerras
2013-04-11 13:45 ` Marcelo Tosatti
2013-04-11 13:45 ` Marcelo Tosatti
2013-04-11 13:50 ` Alexander Graf
2013-04-11 13:50 ` Alexander Graf
2013-04-12 20:54 ` Marcelo Tosatti
2013-04-12 20:54 ` Marcelo Tosatti
2013-04-12 20:56 ` Alexander Graf
2013-04-12 20:56 ` Alexander Graf
2013-04-16 17:26 ` Alexander Graf
2013-04-16 17:26 ` Alexander Graf
2013-04-16 21:28 ` Marcelo Tosatti
2013-04-16 21:28 ` Marcelo Tosatti
2013-03-26 16:37 ` Scott Wood
2013-03-26 16:37 ` Scott Wood
2013-03-31 10:49 ` Gleb Natapov
2013-03-31 10:49 ` Gleb Natapov
2013-03-31 11:05 ` Alexander Graf
2013-03-31 11:05 ` Alexander Graf
2013-04-08 18:17 ` Scott Wood
2013-04-08 18:17 ` Scott Wood
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=1364252043.26945.19@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=gleb@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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.