From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: xsm deassign hook Date: Wed, 18 Jul 2012 17:35:29 +0100 Message-ID: <5006E5D1.3070607@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Shakeel Butt Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 18/07/12 17:25, Shakeel Butt wrote: > Hi, > > In xen-4.1-testing.hg at xen/arch/x86/domctl.c:876, xsm_assign_device > should be xsm_deassign_device. In xen-unstable.hg, this code was moved > to xen/drivers/passthrough/iommu.c and got fixed. I am a newbie here > and want to know what is the criteria for moving patches from > xen-unstable to xen-*-testing. Hi. Backports are done by requests on the list, cc'd to keir@xen.org who maintains the -testing repositories. If the unstable patch applies cleanly, just name its changeset with your recommendation, but if it is not a trivial backport, it is generally appreciated if you formulate a patch. In this case however, it should be trivial, so just name the xen-unstable changeset. ~Andrew > > Shakeel > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com