From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mackerras Date: Fri, 22 Feb 2019 09:46:17 +0000 Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag Message-Id: <20190222094617.GG6006@blackberry> List-Id: References: <20190222051405.GA2527@blackberry> In-Reply-To: <20190222051405.GA2527@blackberry> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ppc@vger.kernel.org On Fri, Feb 22, 2019 at 03:46:33PM +0900, Masahiro Yamada wrote: > On Fri, Feb 22, 2019 at 2:52 PM Paul Mackerras wrote: > > > > On Fri, Feb 22, 2019 at 02:23:09PM +0900, Masahiro Yamada wrote: > > > On Fri, Feb 22, 2019 at 2:14 PM Paul Mackerras wrote: > > > > > > > > > > > > > Masahiro Yamada (1): > > > > KVM: PPC: Remove -I. header search paths > > > > > > > > > Michael Ellerman already applied this > > > and I see it in linux-next, though. > > > > Oh well, I didn't notice that, but it doesn't matter anyway because > > the powerpc/next branch merges cleanly with my kvm-ppc-next branch > > (and if it didn't, Stephen Rothwell would have let us know). > > > Yeah, git will merge it nicely, but > please let me state my two cents. > > I like to see "applied" email from a maintainer. > > Michael replied to me (and ML) when he applied my patch. I normally do that too, though I do it manually (I think Michael has an automated process), and this time my collecting of patches got delayed because I was chasing a nasty memory corruption bug. I have asked Michael to cc me when he applies a KVM patch to his tree in future. Paul.