From: Arnd Bergmann <arnd@arndb.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Andre Przywara <Andre.Przywara@arm.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] PCI: Fix pcibios_update_irq misuse of irq number
Date: Tue, 03 Feb 2015 13:57:17 +0100 [thread overview]
Message-ID: <47577254.MGNlDcIDBf@wuerfel> (raw)
In-Reply-To: <54D0B2FA.9080600@arm.com>
On Tuesday 03 February 2015 11:37:30 Marc Zyngier wrote:
> Side question: In the probe-only case, should we still allow this write
> to happen?
No, my understanding is that PCI_PROBE_ONLY precisely means that we
do not modify the config space and instead trust what is there to
be sensible.
Arnd
prev parent reply other threads:[~2015-02-03 12:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 14:51 [PATCH] PCI: Fix pcibios_update_irq misuse of irq number Marc Zyngier
2015-01-28 15:21 ` Jiang Liu
2015-01-28 15:27 ` Marc Zyngier
2015-01-28 15:43 ` Bjorn Helgaas
2015-02-02 16:15 ` Marc Zyngier
2015-02-02 16:22 ` Bjorn Helgaas
2015-02-02 15:57 ` Bjorn Helgaas
2015-02-02 16:06 ` Jiang Liu
2015-02-02 16:23 ` Marc Zyngier
2015-02-02 16:33 ` Russell King - ARM Linux
2015-02-02 18:08 ` Marc Zyngier
2015-02-02 18:20 ` Russell King - ARM Linux
2015-02-02 17:02 ` Arnd Bergmann
2015-02-03 10:38 ` Marc Zyngier
2015-02-03 11:31 ` Arnd Bergmann
2015-02-03 11:37 ` Marc Zyngier
2015-02-03 12:57 ` Arnd Bergmann [this message]
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=47577254.MGNlDcIDBf@wuerfel \
--to=arnd@arndb.de \
--cc=Andre.Przywara@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/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).