WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 17/17] xen: disable MSI

To: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 17/17] xen: disable MSI
From: Roland Dreier <rdreier@xxxxxxxxx>
Date: Thu, 28 May 2009 15:21:14 -0700
Authentication-results: sj-dkim-1; header.From=rdreier@xxxxxxxxx; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: Chris Wright <chrisw@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ky Srinivasan <ksrinivasan@xxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, Avi Kivity <avi@xxxxxxxxxx>, Jens Axboe <jens.axboe@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Greg KH <gregkh@xxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 28 May 2009 15:21:45 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=542; t=1243549278; x=1244413278; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdreier@xxxxxxxxx; z=From:=20Roland=20Dreier=20<rdreier@xxxxxxxxx> |Subject:=20Re=3A=20[PATCH=2017/17]=20xen=3A=20disable=20MS I |Sender:=20; bh=66DDOAHov54sDHJ1CBUzOYpgJ6jZO+pSJXpfsYEWHCM=; b=E61ja+yE6BOYqrQ/dqXx5Mblleixc9OYT1zB8SiwGf13CwIX+sxgJLjiWk FJBcJVRpswrXUsK3YxRf1hJBelnFdEG/YlYp8ow/LCScYBGvhTuqr048GBWm RHwbtq8jW4v5rlw6S2BdqOggbPf3cMUrs+1QpaaTZ3LwH351cLXzc=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090527233807.e7e39e97.akpm@xxxxxxxxxxxxxxxxxxxx> (Andrew Morton's message of "Wed, 27 May 2009 23:38:07 -0700")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1243409850-21577-1-git-send-email-jeremy@xxxxxxxx> <1243409850-21577-18-git-send-email-jeremy@xxxxxxxx> <alpine.LFD.2.01.0905270829530.3435@xxxxxxxxxxxxxxxxxxxxx> <20090527211828.GA6166@xxxxxxx> <alpine.LFD.2.01.0905271436140.3435@xxxxxxxxxxxxxxxxxxxxx> <adavdnm5hkx.fsf@xxxxxxxxx> <20090528072844.4c1db656@xxxxxxxxxxxxxxxxxxx> <20090527233807.e7e39e97.akpm@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux)
 > Yup.  I presently use "Addresses: <url>" in the changelog.
 > 
 > y:/usr/src/git26> git-log | grep '^    Addresses.*bugzilla' | wc -l
 > 36
 > 
 > Formalising that a bit more would be good.
 > 
 > Not all patches literally "close" a bugzilla report though.  Sometimes
 > there's related info in bugzilla but the bug remains.  But
 > "closes-bug:" is close enough.

Yes, I deliberately didn't suggest "Fixes-bug:" but I like your
"Addresses:" language even better.  I'll start using that for any
commits from now on.

 - R.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel