From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm-ppc@vger.kernel.org
Subject: Re: Fwd: [PULL 00/56] ppc patch queue 2012-10-04
Date: Sun, 07 Oct 2012 10:37:46 +0000 [thread overview]
Message-ID: <50715B7A.8050401@redhat.com> (raw)
In-Reply-To: <BF0ACF60-A936-4E8A-BF6C-AD6A11581E65@suse.de>
On 10/05/2012 11:21 PM, Alexander Graf wrote:
> Hi Avi / Marcelo,
>
> Apparently I messed up while sending the pull request yesterday and didn't CC kvm@vger. Do you want me to resend or is this good enough for you? :)
This is fine now you've copied the list. Do any of the "small bug
fixes" want to be in 3.7? If so you need to split them off into their
own branch.
>
>
> Alex
>
> Begin forwarded message:
>
>> From: Alexander Graf <agraf@suse.de>
>> Subject: [PULL 00/56] ppc patch queue 2012-10-04
>> Date: 4. Oktober 2012 15:36:28 MESZ
>> To: kvm-ppc@vger.kernel.org
>>
>> Hi Avi / Marcelo,
>>
>> This is my current patch queue for ppc. Please pull.
>>
>> Changes include:
>>
>> * add support for idle hcall on booke
>> * icache clear on map
>> * mmu notifier support for e500 and book3s_pr
>> * revive the 440 support slightly (still not 100% happy)
>> * unify booke and book3s_pr entry/exit code a bit
>> * add watchdog emulation for booke
>> * reset and migratbility fixes for book3s_64_hv
>> * rework book3s_64_hv memslot locking
>> * small bug fixes
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm-ppc@vger.kernel.org
Subject: Re: Fwd: [PULL 00/56] ppc patch queue 2012-10-04
Date: Sun, 07 Oct 2012 12:37:46 +0200 [thread overview]
Message-ID: <50715B7A.8050401@redhat.com> (raw)
In-Reply-To: <BF0ACF60-A936-4E8A-BF6C-AD6A11581E65@suse.de>
On 10/05/2012 11:21 PM, Alexander Graf wrote:
> Hi Avi / Marcelo,
>
> Apparently I messed up while sending the pull request yesterday and didn't CC kvm@vger. Do you want me to resend or is this good enough for you? :)
This is fine now you've copied the list. Do any of the "small bug
fixes" want to be in 3.7? If so you need to split them off into their
own branch.
>
>
> Alex
>
> Begin forwarded message:
>
>> From: Alexander Graf <agraf@suse.de>
>> Subject: [PULL 00/56] ppc patch queue 2012-10-04
>> Date: 4. Oktober 2012 15:36:28 MESZ
>> To: kvm-ppc@vger.kernel.org
>>
>> Hi Avi / Marcelo,
>>
>> This is my current patch queue for ppc. Please pull.
>>
>> Changes include:
>>
>> * add support for idle hcall on booke
>> * icache clear on map
>> * mmu notifier support for e500 and book3s_pr
>> * revive the 440 support slightly (still not 100% happy)
>> * unify booke and book3s_pr entry/exit code a bit
>> * add watchdog emulation for booke
>> * reset and migratbility fixes for book3s_64_hv
>> * rework book3s_64_hv memslot locking
>> * small bug fixes
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-07 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 13:36 [PULL 00/56] ppc patch queue 2012-10-04 Alexander Graf
2012-10-05 21:21 ` Fwd: " Alexander Graf
2012-10-05 21:21 ` Alexander Graf
2012-10-07 10:37 ` Avi Kivity [this message]
2012-10-07 10:37 ` 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=50715B7A.8050401@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--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.