From: Paolo Bonzini <pbonzini@redhat.com> To: Paul Mackerras <paulus@ozlabs.org>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org, Michael Ellerman <michael@ellerman.id.au> Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes branch Date: Thu, 2 Mar 2017 12:00:44 +0100 [thread overview] Message-ID: <31cab3d3-8ef2-11bc-7091-73c9e0103693@redhat.com> (raw) In-Reply-To: <20170302015556.GA25913@fergus.ozlabs.ibm.com> On 02/03/2017 02:55, Paul Mackerras wrote: > Paolo, > > Please do a pull from my kvm-ppc-fixes branch to get two bug fixes for > HV KVM on POWER9 machines. I would like them to go into 4.11. > > One of the commits touches a PPC header file. I have verbal approval > from Michael Ellerman for this change to go via the KVM tree because > the affected definitions are only used by KVM. Fair enough! Conflicts are only really an issue for the first pull request in the merge window. Paolo > Thanks, > Paul. > > The following changes since commit fd7e9a88348472521d999434ee02f25735c7dadf: > > Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2017-02-22 18:22:53 -0800) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc kvm-ppc-fixes > > for you to fetch changes up to 4e5acdc23a3dcbd6ad6dc93a9783dd9c838987c8: > > KVM: PPC: Book3S HV: Don't use ASDR for real-mode HPT faults on POWER9 (2017-03-01 11:54:10 +1100)
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com> To: Paul Mackerras <paulus@ozlabs.org>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org, Michael Ellerman <michael@ellerman.id.au> Subject: Re: [GIT PULL] Please pull my kvm-ppc-fixes branch Date: Thu, 02 Mar 2017 11:00:44 +0000 [thread overview] Message-ID: <31cab3d3-8ef2-11bc-7091-73c9e0103693@redhat.com> (raw) In-Reply-To: <20170302015556.GA25913@fergus.ozlabs.ibm.com> On 02/03/2017 02:55, Paul Mackerras wrote: > Paolo, > > Please do a pull from my kvm-ppc-fixes branch to get two bug fixes for > HV KVM on POWER9 machines. I would like them to go into 4.11. > > One of the commits touches a PPC header file. I have verbal approval > from Michael Ellerman for this change to go via the KVM tree because > the affected definitions are only used by KVM. Fair enough! Conflicts are only really an issue for the first pull request in the merge window. Paolo > Thanks, > Paul. > > The following changes since commit fd7e9a88348472521d999434ee02f25735c7dadf: > > Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2017-02-22 18:22:53 -0800) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc kvm-ppc-fixes > > for you to fetch changes up to 4e5acdc23a3dcbd6ad6dc93a9783dd9c838987c8: > > KVM: PPC: Book3S HV: Don't use ASDR for real-mode HPT faults on POWER9 (2017-03-01 11:54:10 +1100)
next prev parent reply other threads:[~2017-03-02 11:00 UTC|newest] Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-02 1:55 [GIT PULL] Please pull my kvm-ppc-fixes branch Paul Mackerras 2017-03-02 1:55 ` Paul Mackerras 2017-03-02 11:00 ` Paolo Bonzini [this message] 2017-03-02 11:00 ` Paolo Bonzini 2017-03-02 21:04 ` Radim Krčmář 2017-03-02 21:04 ` Radim Krčmář -- strict thread matches above, loose matches on Subject: below -- 2017-10-19 4:20 Paul Mackerras 2017-10-19 4:20 ` Paul Mackerras 2017-10-19 13:11 ` Radim Krčmář 2017-10-19 13:11 ` Radim Krčmář 2017-09-14 4:06 Paul Mackerras 2017-09-14 4:06 ` Paul Mackerras 2017-08-30 6:21 Paul Mackerras 2017-08-30 6:21 ` Paul Mackerras 2017-09-08 14:37 ` Radim Krčmář 2017-09-08 14:37 ` Radim Krčmář 2017-09-09 13:38 ` Paolo Bonzini 2017-09-09 13:38 ` Paolo Bonzini 2017-09-12 4:01 ` Paul Mackerras 2017-09-12 4:01 ` Paul Mackerras 2017-08-25 1:38 Paul Mackerras 2017-08-25 1:38 ` Paul Mackerras 2017-08-25 7:02 ` Paolo Bonzini 2017-08-25 7:02 ` Paolo Bonzini 2017-08-25 9:06 ` Paul Mackerras 2017-08-25 9:06 ` Paul Mackerras 2017-07-26 4:43 Paul Mackerras 2017-07-26 4:43 ` Paul Mackerras 2017-07-01 10:11 [GIT PULL] Please pull my kvm-ppc-fixes branch again Paul Mackerras 2017-07-01 10:11 ` Paul Mackerras 2017-07-03 8:40 ` Paolo Bonzini 2017-07-03 8:40 ` Paolo Bonzini 2017-07-05 6:54 ` Paul Mackerras 2017-07-05 6:54 ` Paul Mackerras 2017-06-20 4:30 [GIT PULL] Please pull my kvm-ppc-fixes branch Paul Mackerras 2017-06-20 4:30 ` Paul Mackerras 2017-06-20 12:39 ` Radim Krčmář 2017-06-20 12:39 ` Radim Krčmář 2017-06-20 12:55 ` Paolo Bonzini 2017-06-20 12:55 ` Paolo Bonzini 2017-06-20 15:17 ` Radim Krčmář 2017-06-20 15:17 ` Radim Krčmář 2017-06-20 23:37 ` Paul Mackerras 2017-06-20 23:37 ` Paul Mackerras 2017-06-21 10:30 ` Paolo Bonzini 2017-06-21 10:30 ` Paolo Bonzini 2017-05-15 8:16 Paul Mackerras 2017-05-15 8:16 ` Paul Mackerras 2017-05-15 8:32 ` Christian Zigotzky 2017-05-15 8:32 ` Christian Zigotzky 2017-05-16 13:52 ` Radim Krčmář 2017-05-16 13:52 ` Radim Krčmář 2017-04-06 6:28 Paul Mackerras 2017-04-06 6:28 ` Paul Mackerras 2017-04-06 14:37 ` Radim Krčmář 2017-04-06 14:37 ` Radim Krčmář 2016-03-08 10:54 Paul Mackerras 2016-03-08 10:54 ` Paul Mackerras 2015-12-10 3:12 Paul Mackerras 2015-12-10 3:12 ` Paul Mackerras 2015-12-11 11:30 ` Paolo Bonzini 2015-12-11 11:30 ` Paolo Bonzini 2015-11-12 5:35 Paul Mackerras 2015-11-12 5:35 ` Paul Mackerras 2015-11-12 9:11 ` Paolo Bonzini 2015-11-12 9:11 ` 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=31cab3d3-8ef2-11bc-7091-73c9e0103693@redhat.com \ --to=pbonzini@redhat.com \ --cc=kvm-ppc@vger.kernel.org \ --cc=kvm@vger.kernel.org \ --cc=michael@ellerman.id.au \ --cc=paulus@ozlabs.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: linkBe 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.