From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
To: Marc Zyngier <marc.zyngier@arm.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Robin Murphy <robin.murphy@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
David Laight <david.laight@aculab.com>,
linux-pci <linux-pci@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
LKML <linux-kernel@vger.kernel.org>, Mason <slash.tmp@free.fr>
Subject: Re: [PATCH v5 2/3] PCI: Add tango PCIe host bridge support
Date: Mon, 19 Jun 2017 18:01:15 +0200 [thread overview]
Message-ID: <e45533a7-e469-7faf-4b30-acf6889b982c@sigmadesigns.com> (raw)
In-Reply-To: <7d9bfb52-b33a-79ea-dccf-fff1f849bd15@arm.com>
On 19/06/2017 17:58, Marc Zyngier wrote:
> On 19/06/17 15:50, Marc Gonzalez wrote:
>> On 07/06/2017 10:19, Marc Gonzalez wrote:
>>
>>> On 31/05/2017 15:33, Marc Gonzalez wrote:
>>>
>>>> +static int tango_pcie_probe(struct platform_device *pdev)
>>>> +{
>>>> + int ret = -EINVAL;
>>>> + void __iomem *base;
>>>> + struct resource *res;
>>>> + struct tango_pcie *pcie;
>>>> + struct device *dev = &pdev->dev;
>>>> +
>>>> + pr_err("MAJOR ISSUE: PCIe config and mem spaces are muxed\n");
>>>> + pr_err("Tainting kernel... Use driver at your own risk\n");
>>>> + add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK);
>>>
>>> Hello Bjorn,
>>>
>>> In v4, your only comment was
>>> "[muxing config and mem spaces] is a major issue and possibly even
>>> a security problem [which requires at least an error message and a
>>> kernel taint].
>>>
>>> Were there any other issues with the host bridge support?
>>
>> Hello Bjorn,
>>
>> I imagine you are now only waiting for Marc Z's Ack of patch 3/3 ?
>> (AFAIU, all issues have been addressed as of v8 3/3.)
>
> Posting partial series is really not ideal, specially as you posted 3 of
> them in less than 24 hours (and the latest was only 5 days ago).
>
> The maintainer is not going to chase you about potentially missing
> patches...
So the best course would be posting a new series with all patches
bumped to v8 then?
Regards.
next prev parent reply other threads:[~2017-06-19 16:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 13:28 [PATCH v5 0/3] Tango PCIe controller support Marc Gonzalez
2017-05-31 13:30 ` [PATCH v5 1/3] PCI: Add DT binding for tango PCIe controller Marc Gonzalez
2017-06-07 21:29 ` Rob Herring
2017-06-07 22:34 ` Mason
2017-06-13 11:55 ` Marc Zyngier
2017-06-13 14:23 ` Rob Herring
2017-06-13 13:51 ` [PATCH v6 " Marc Gonzalez
2017-06-18 14:05 ` Rob Herring
2017-05-31 13:33 ` [PATCH v5 2/3] PCI: Add tango PCIe host bridge support Marc Gonzalez
2017-06-07 8:19 ` Marc Gonzalez
2017-06-19 14:50 ` Marc Gonzalez
2017-06-19 15:58 ` Marc Zyngier
2017-06-19 16:01 ` Marc Gonzalez [this message]
2017-06-19 16:16 ` Marc Zyngier
2017-06-20 8:29 ` Marc Gonzalez
2017-07-05 9:36 ` Ard Biesheuvel
2017-07-05 12:18 ` Marc Gonzalez
2017-05-31 13:35 ` [PATCH v5 3/3] PCI: Add tango MSI controller support Marc Gonzalez
2017-06-13 12:09 ` Marc Zyngier
2017-06-13 14:01 ` [PATCH v6 " Marc Gonzalez
2017-06-13 14:22 ` Marc Zyngier
2017-06-13 14:47 ` Marc Gonzalez
2017-06-13 16:53 ` Marc Zyngier
2017-06-14 9:00 ` [PATCH v7 " Marc Gonzalez
2017-06-14 9:19 ` Marc Gonzalez
2017-06-14 9:32 ` Marc Zyngier
2017-06-14 11:06 ` [PATCH v8 " Marc Gonzalez
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=e45533a7-e469-7faf-4b30-acf6889b982c@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.com \
--cc=david.laight@aculab.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=robin.murphy@arm.com \
--cc=slash.tmp@free.fr \
--cc=tglx@linutronix.de \
--cc=thibaud_cornic@sigmadesigns.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
all inboxes | Powered by JetHome®