From: Joerg Roedel <joro@8bytes.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Don Dutile <ddutile@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Prarit Bhargava <prarit@redhat.com>,
Don Zickus <dzickus@redhat.com>,
Asit Mallick <asit.k.mallick@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH v6] irq: add quirk for broken interrupt remapping on 55XX chipsets
Date: Tue, 9 Apr 2013 12:08:01 +0200 [thread overview]
Message-ID: <20130409100801.GF6858@8bytes.org> (raw)
In-Reply-To: <20130408174257.GA13960@hmsreliant.think-freely.org>
On Mon, Apr 08, 2013 at 01:42:57PM -0400, Neil Horman wrote:
> On Mon, Apr 08, 2013 at 11:17:23AM -0600, Bjorn Helgaas wrote:
> > I don't care whether the "if (irq_remap_broken)" test is in
> > irq_remapping.c or intel_irq_remapping.c. The quirk itself, where we
> > actually look at config space, is clearly Intel-specific, but there
> > could easily be similar AMD quirks that could also set
> > irq_remap_broken. In that case, it would make sense to have the test
> > in the common code.
> >
> I've moved it to intel specific code for the time being, since it currently is
> intel specific, its an easy move to put it in a common location if other vendors
> have a need for it.
>
> I'm currently waiting on aproval to make the bz public, so that its inclusion in
> the changelog is more than just an irritation when following the link results in
> a 403 error. As soon as thats square, I'll post this again, CC-ing Jeorg and
> Konrad.
Thanks Neil. As long as this quirk is intel specific it should be in
the intel-code.
Joerg
next prev parent reply other threads:[~2013-04-09 10:08 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 17:17 [PATCH] irq: add quirk for broken interrupt remapping on 55XX chipsets Neil Horman
2013-03-01 18:20 ` Yinghai Lu
2013-03-01 19:29 ` Neil Horman
2013-03-02 2:28 ` Jiang Liu
2013-03-02 15:59 ` Andreas Mohr
2013-03-04 13:24 ` Don Dutile
2013-03-10 1:11 ` Prarit Bhargava
2013-03-02 16:21 ` Prarit Bhargava
2013-03-02 20:13 ` Neil Horman
2013-03-04 19:04 ` [PATCH v2] " Neil Horman
2013-03-09 20:49 ` Neil Horman
2013-03-09 22:20 ` Myron Stowe
2013-03-11 1:31 ` Don Dutile
2013-03-11 11:25 ` Neil Horman
2013-03-11 12:17 ` Prarit Bhargava
2013-04-03 23:53 ` Bjorn Helgaas
2013-04-04 11:17 ` Neil Horman
2013-04-04 14:27 ` David Woodhouse
2013-04-04 14:50 ` Neil Horman
2013-04-04 14:57 ` Bjorn Helgaas
2013-04-04 15:39 ` Neil Horman
2013-04-04 17:14 ` Bjorn Helgaas
2013-04-04 17:51 ` Neil Horman
2013-04-04 18:41 ` Bjorn Helgaas
2013-04-04 20:02 ` Neil Horman
2013-04-04 13:54 ` [PATCH v3] " Neil Horman
2013-04-04 15:08 ` [PATCH v4] " Neil Horman
2013-04-04 16:16 ` Yinghai Lu
2013-04-04 17:27 ` Don Dutile
2013-04-04 17:40 ` Yinghai Lu
2013-04-04 20:04 ` Neil Horman
2013-04-04 20:33 ` Bjorn Helgaas
2013-04-04 21:11 ` Yinghai Lu
2013-04-05 0:24 ` Neil Horman
2013-04-05 19:25 ` [PATCH v5] " Neil Horman
2013-04-05 19:29 ` Neil Horman
2013-04-05 19:31 ` [PATCH v6] " Neil Horman
2013-04-05 23:37 ` Yinghai Lu
2013-04-06 1:55 ` Bjorn Helgaas
2013-04-08 15:29 ` Don Dutile
2013-04-08 17:17 ` Bjorn Helgaas
2013-04-08 17:42 ` Neil Horman
2013-04-09 10:08 ` Joerg Roedel [this message]
2013-04-15 11:18 ` [PATCH v7] " Neil Horman
2013-04-15 15:30 ` Bjorn Helgaas
2013-04-15 16:28 ` Neil Horman
2013-04-15 16:28 ` [PATCH v8] " Neil Horman
2013-04-15 22:41 ` [PATCH v9] " Neil Horman
2013-04-15 23:02 ` Yinghai Lu
2013-04-16 0:43 ` Neil Horman
2013-04-16 6:20 ` Arkadiusz Miskiewicz
2013-04-16 10:24 ` Joerg Roedel
2013-04-16 13:07 ` Neil Horman
2013-04-16 13:35 ` Neil Horman
2013-04-16 16:37 ` Joerg Roedel
2013-04-16 17:25 ` Neil Horman
2013-04-16 20:38 ` [PATCH v10] " Neil Horman
2013-04-16 22:08 ` Don Dutile
2013-04-18 15:02 ` Joerg Roedel
2013-04-18 17:00 ` Neil Horman
-- strict thread matches above, loose matches on Subject: below --
2013-04-06 1:25 [PATCH v6] " Neil Horman
2013-04-06 2:32 ` Yinghai Lu
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=20130409100801.GF6858@8bytes.org \
--to=joro@8bytes.org \
--cc=asit.k.mallick@intel.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=dzickus@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=prarit@redhat.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