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: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 17/17] xen: disable MSI
From: Roland Dreier <rdreier@xxxxxxxxx>
Date: Wed, 27 May 2009 15:20:46 -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>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, 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>, Greg KH <gregkh@xxxxxxx>
Delivery-date: Thu, 28 May 2009 06:30:08 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=410; t=1243462847; x=1244326847; 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=XMfqMUStOShdRgQMkjyKACN6P0yFF9ujkP6/PTQ+hzQ=; b=Pf1VXyKJG0bL01/hEnncjZhYrNjQ/LRsquU0WhpXVvxBWBxVW8a5lpkBWv ALSutmeehO/pumMgPSCLoSJlJGmniByw4CSImQXV1dZ/wQydbiPPb4ml+5TF sVGG11KUVRVjgmV7s1yocjGBx3ymda0ExccqfRLtB+Ozk/b2Dzi0s=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.LFD.2.01.0905271511440.3435@xxxxxxxxxxxxxxxxxxxxx> (Linus Torvalds's message of "Wed, 27 May 2009 15:13:10 -0700 (PDT)")
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> <alpine.LFD.2.01.0905271511440.3435@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux)
 > I agree that that would work, but that way also lies endless other tags. 
 > People seem to always want to have some magic tag to grep for, if we can 
 > make 'impact:' be it rather than have potentially lots of random ones, 
 > maybe impact: is simply better?

Dunno... maybe just "Tag:"?  ;)

Maybe just "git log|grep 'bug url'" is good enough without having to
make any special format?

 - R.

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