From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: [GIT PULL] MIPS KVM fix for v4.9-rc2 Date: Fri, 21 Oct 2016 20:52:29 +0200 Message-ID: <20161021185228.GA25783@potion> References: <1476971554-1215-1-git-send-email-james.hogan@imgtec.com> <20161020180449.GC8569@potion> <20161020192657.GN7370@jhogan-linux.le.imgtec.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , Ralf Baechle , linux-mips@linux-mips.org, kvm@vger.kernel.org To: James Hogan Return-path: Received: from mx1.redhat.com ([209.132.183.28]:47092 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934815AbcJUSwd (ORCPT ); Fri, 21 Oct 2016 14:52:33 -0400 Content-Disposition: inline In-Reply-To: <20161020192657.GN7370@jhogan-linux.le.imgtec.org> Sender: kvm-owner@vger.kernel.org List-ID: 2016-10-20 20:26+0100, James Hogan: > What is the queue branch for? It is a staging branch. All patches applied by Paolo or me usually start in kvm/queue. Applying to kvm/queue means that we think that the patch is ok, but it is by no means final -- the on-list review continues and we add r-b tags, do minimal changes, or even drop patches according to feedback. Patches are tested in kvm/queue before being included in a permanent branch.