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: Ingo Molnar <mingo@xxxxxxx>
Subject: [Xen-devel] Re: [PATCH 17/17] xen: disable MSI
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 27 May 2009 14:46:15 -0700 (PDT)
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>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Greg KH <gregkh@xxxxxxx>
Delivery-date: Thu, 28 May 2009 06:27:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090527211828.GA6166@xxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.01 (LFD 1184 2008-12-16)

On Wed, 27 May 2009, Ingo Molnar wrote:
> 
> hm, i have to concur. Too often it ends up splitting attention away 
> from the title of the commit. I do reject (or fix up) bad impact 
> lines - will stop doing them altogether if you think there's a net 
> downside to them ...

I actually think that if there is a good reason for them, they can stay. 

Just don't make it one of those "every commit that goes through me has to 
have one".

Pu another way: if they actually add value in highlighting the commits 
that _should_ stand out, then hey, by all means, keep such ones. I would 
not at all object if it was an issue of 

 [ Impact: fix bugzilla entry 455123 ]

or

 [ Impact: fix user-triggerable oops ]

or something that actually matters, and that you _want_ to stand out, and 
that you may well _want_ to grep for.

It's when the whole series has them, and they don't add anything that 
isn't better said in the summary line, _that's_ what I dislike.

So to take the above bugzilla example: it really wouldn't be a good 
summary line (because the summary line should describe what the commit 
does, not point to some bugzilla entry), but at the same time it's clearly 
something that I do think we might want to automate the logs for.

IOW, that is something even I personally wouldn't mind adding to a commit, 
to help people like Rafael that track bugzilla. It makes sense as a 
special marker, even though it clearly _shoudln't_ be the summary. See?

Similarly, the "user-triggerable oops" might well be worth high-lighting 
in some manner. Now, the summary _might_ talk about it, but equally well 
the summary might be more specific in the actual implementation issue, and 
then perhaps the impact line is worth it.

But if all commits have them (at least for the x86-tip), then it's not a 
really highlight event any more, is it? At that point, anything it says is 
probably just as well described by the summary line - at least for any 
"regular" commits that aren't in some way worth the extra attention.

                        Linus

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

<Prev in Thread] Current Thread [Next in Thread>