From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <rth@twiddle.net>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH v2] memory_mapping: Rework cpu related includes
Date: Wed, 17 Jun 2015 10:57:15 +0200 [thread overview]
Message-ID: <5581366B.3010302@redhat.com> (raw)
In-Reply-To: <CAEgOgz6md-U4nAZM1MEqAqMnt6wk4APhGuU5tptXijq0umZQ+Q@mail.gmail.com>
On 09/06/2015 09:42, Peter Crosthwaite wrote:
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> >
> > About to leave on vacation, so someone else will have to pick it up.
>
> Enjoy. If you are not back before soft freeze would you object to me
> sending a [PULL] for some of the multi-arch related mainloop header
> patches for which I have RB from Richard from?
I don't object to you sending a pull request for any multi-arch related
changes. Anything that makes fewer patches go through my "misc" pull
requests is a good thing for me.
Just consult with Andreas when he's back about what he prefers to go
through his tree.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <rth@twiddle.net>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] memory_mapping: Rework cpu related includes
Date: Wed, 17 Jun 2015 10:57:15 +0200 [thread overview]
Message-ID: <5581366B.3010302@redhat.com> (raw)
In-Reply-To: <CAEgOgz6md-U4nAZM1MEqAqMnt6wk4APhGuU5tptXijq0umZQ+Q@mail.gmail.com>
On 09/06/2015 09:42, Peter Crosthwaite wrote:
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> >
> > About to leave on vacation, so someone else will have to pick it up.
>
> Enjoy. If you are not back before soft freeze would you object to me
> sending a [PULL] for some of the multi-arch related mainloop header
> patches for which I have RB from Richard from?
I don't object to you sending a pull request for any multi-arch related
changes. Anything that makes fewer patches go through my "misc" pull
requests is a good thing for me.
Just consult with Andreas when he's back about what he prefers to go
through his tree.
Paolo
next prev parent reply other threads:[~2015-06-17 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 21:59 [Qemu-trivial] [PATCH v2] memory_mapping: Rework cpu related includes Peter Crosthwaite
2015-06-07 21:59 ` [Qemu-devel] " Peter Crosthwaite
2015-06-08 10:47 ` [Qemu-trivial] " Paolo Bonzini
2015-06-08 10:47 ` [Qemu-devel] " Paolo Bonzini
2015-06-09 7:42 ` [Qemu-trivial] " Peter Crosthwaite
2015-06-09 7:42 ` Peter Crosthwaite
2015-06-17 8:57 ` Paolo Bonzini [this message]
2015-06-17 8:57 ` Paolo Bonzini
2015-06-24 4:33 ` [Qemu-trivial] " Peter Crosthwaite
2015-06-24 4:33 ` Peter Crosthwaite
2015-06-24 8:54 ` [Qemu-trivial] " Paolo Bonzini
2015-06-24 8:54 ` [Qemu-devel] " Paolo Bonzini
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=5581366B.3010302@redhat.com \
--to=pbonzini@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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.