From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: jeremy@goop.org, mingo@elte.hu, x86@kernel.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
gregkh@suse.de, jens.axboe@oracle.com, chrisw@redhat.com,
kurt.hackel@oracle.com, akpm@linux-foundation.org,
ksrinivasan@novell.com, jbeulich@novell.com, avi@redhat.com,
jeremy.fitzhardinge@citrix.com
Subject: Re: [PATCH 17/17] xen: disable MSI
Date: Wed, 27 May 2009 13:40:06 -0700 (PDT) [thread overview]
Message-ID: <20090527.134006.241271867.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.01.0905270829530.3435@localhost.localdomain>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed, 27 May 2009 08:34:22 -0700 (PDT)
> I hate them. They are stupid. 90% of all the impact lines I see are either
> (a) misleading or (b) totally inane and pointless.
I just delete any Impact lines I see in patches sent to me, and I
honestly suggest you do so as well.
Really.
next prev parent reply other threads:[~2009-05-27 20:40 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 [this message]
2009-05-27 22:25 ` Ingo Molnar
2009-05-27 21:18 ` Ingo Molnar
2009-05-27 21:46 ` Linus Torvalds
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=20090527.134006.241271867.davem@davemloft.net \
--to=davem@davemloft.net \
--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=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).