From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Greg KH <gregkh@suse.de>, Jens Axboe <jens.axboe@oracle.com>,
Chris Wright <chrisw@redhat.com>,
kurt.hackel@oracle.com, Andrew Morton <akpm@linux-foundation.org>,
Ky Srinivasan <ksrinivasan@novell.com>,
Beulich <jbeulich@novell.com>, Avi Kivity <avi@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 17/17] xen: disable MSI
Date: Wed, 27 May 2009 14:46:15 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0905271436140.3435@localhost.localdomain> (raw)
In-Reply-To: <20090527211828.GA6166@elte.hu>
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
next prev parent reply other threads:[~2009-05-27 21:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 7:37 [GIT PULL REPOST] xen/dom0/apic-ops: Xen dom0 APIC changes Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 01/17] xen/dom0: handle acpi lapic parsing in Xen dom0 Jeremy Fitzhardinge
2009-06-02 16:58 ` Thomas Gleixner
2009-06-03 6:38 ` Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 02/17] x86: add io_apic_ops to allow interception Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 03/17] xen: implement io_apic_ops Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 04/17] xen: create dummy ioapic mapping Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 05/17] xen: implement pirq type event channels Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 06/17] x86/io_apic: add get_nr_irqs_gsi() Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 07/17] xen/apic: identity map gsi->irqs Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 08/17] xen: direct irq registration to pirq event channels Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 09/17] xen: bind pirq to vector and event channel Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 10/17] xen: pre-initialize legacy irqs early Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 11/17] xen: don't setup acpi interrupt unless there is one Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 12/17] xen: use acpi_get_override_irq() to get triggering for legacy irqs Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 13/17] xen: initialize irq 0 too Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 14/17] xen: dynamically allocate irq & event structures Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 15/17] xen: set pirq name to something useful Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 16/17] xen: fix legacy irq setup, make ioapic-less machines work Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 17/17] xen: disable MSI Jeremy Fitzhardinge
2009-05-27 15:34 ` Linus Torvalds
2009-05-27 20:40 ` David Miller
2009-05-27 22:25 ` Ingo Molnar
2009-05-27 21:18 ` Ingo Molnar
2009-05-27 21:46 ` Linus Torvalds [this message]
2009-05-27 22:01 ` Ingo Molnar
2009-05-27 22:03 ` Roland Dreier
2009-05-27 22:13 ` Linus Torvalds
2009-05-27 22:20 ` Roland Dreier
2009-05-27 22:26 ` Ingo Molnar
2009-05-28 6:28 ` Alan Cox
2009-05-28 6:38 ` Andrew Morton
2009-05-28 22:21 ` Roland Dreier
2009-06-01 2:09 ` Jon Masters
2009-05-28 19:51 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 23:25 [GIT PULL] Xen APIC hooks (with io_apic_ops) Jeremy Fitzhardinge
2009-05-12 23:25 ` [PATCH 17/17] xen: disable MSI Jeremy Fitzhardinge
2009-03-13 16:42 [GIT PULL] Xen dom0 apic changes Jeremy Fitzhardinge
2009-03-13 16:42 ` [PATCH 17/17] xen: disable MSI Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.01.0905271436140.3435@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=gregkh@suse.de \
--cc=jbeulich@novell.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=ksrinivasan@novell.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome