From: Borislav Petkov <email@example.com> To: Paolo Bonzini <firstname.lastname@example.org> Cc: Linus Torvalds <email@example.com>, Sean Christopherson <firstname.lastname@example.org>, Xiaoyao Li <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, KVM list <email@example.com> Subject: Re: [GIT PULL] First batch of KVM changes for 5.6 merge window Date: Fri, 31 Jan 2020 22:24:04 +0100 [thread overview] Message-ID: <20200131212404.GD14851@zn.tnic> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, Jan 31, 2020 at 10:08:10PM +0100, Paolo Bonzini wrote: > I was supposed to get a topic branch and fix everything up so that both > CPU_BASED_ and VMX_FEATURE_ constants would get the new naming. When > Boris alerted me of the conflict and I said "thanks I'll sort it out", > he probably interpreted it as me not needing the topic branch anymore. > I then forgot to remind him, and here we are. Damn, that was a misunderstanding. I actually had a topic branch: tip:x86/cpu and was assuming that you'll see it from the tip-bot notifications. But they went to lkml and you weren't CCed. And regardless, I should've told you explicitly which one it is, sorry about that. I'll be more explicit next time. Thx. -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-01-31 21:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-30 18:20 Paolo Bonzini 2020-01-31 18:01 ` Linus Torvalds 2020-01-31 18:53 ` Sean Christopherson 2020-01-31 19:03 ` Linus Torvalds 2020-01-31 21:08 ` Paolo Bonzini 2020-01-31 21:24 ` Borislav Petkov [this message] 2020-01-31 21:27 ` Paolo Bonzini 2020-01-31 19:35 ` pr-tracker-bot
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=20200131212404.GD14851@zn.tnic \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GIT PULL] First batch of KVM changes for 5.6 merge window' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).