From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Jayachandran Chandrashekaran Nair
<jayachandran.chandrashekaran@broadcom.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Jayachandran C <jchandra@broadcom.com>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-acpi@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tomasz Nowicki <tn@semihalf.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v7 5/5] PCI: ACPI: Add a generic ACPI based host controller
Date: Fri, 5 Feb 2016 09:47:40 +0000 [thread overview]
Message-ID: <20160205094740.GA31547@red-moon> (raw)
In-Reply-To: <CAKc_7PXYtFt1MQE-UGO0O5vvQ+xFKa2b5=F8wXB=EN-JUJVzZw@mail.gmail.com>
On Fri, Feb 05, 2016 at 02:05:37PM +0530, Jayachandran Chandrashekaran Nair wrote:
[...]
> pci_host_acpi.c is a generic implementation of these using a sysdata
> pointing to acpi_pci_root_info, and using a pointer to the pci_mmcfg_region
> to access ECAM area, Maybe I can rename this file to
> pci_acpi_host_generic.c to reflect this better.
Maybe you should stop sending this series and work with Tomasz to
get this done, you are confusing everyone and I am really really
annoyed about this.
Do you realize there is no point in having two patch series doing
the same thing and wasting everyone's review time ?
Do you realize he started this work long before you and went through
several rounds of review already (I told you before but in case you
forgot) ?
Tomasz posted a version yesterday, integrating comments following months
of review and testing and I think it is ready to get upstream:
https://lkml.org/lkml/2016/2/4/646
Did you even consider reviewing his code or helping him instead of
churning out more patches doing the *SAME* thing ?
Do you want all of us to go through your code and re-fix what has
already been fixed in Tomasz's series with the end result of missing
yet another merge window ?
This is really annoying, stop it please, really.
Thank you,
Lorenzo
next prev parent reply other threads:[~2016-02-05 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 9:05 [PATCH v7 0/5] ACPI based PCI support for arm64 Jayachandran C
2016-01-29 9:05 ` [PATCH v7 1/5] APCI: MCFG: Move mmcfg_list management to drivers/acpi Jayachandran C
2016-01-29 9:05 ` [PATCH v7 2/5] ACPI: PCI: Support platforms that need pci_remap_iospace Jayachandran C
2016-01-29 9:05 ` [PATCH v7 3/5] PCI: Handle ACPI companion and domain number Jayachandran C
2016-01-29 9:05 ` [PATCH v7 4/5] arm64: pci: Add ACPI support Jayachandran C
2016-01-29 9:05 ` [PATCH v7 5/5] PCI: ACPI: Add a generic ACPI based host controller Jayachandran C
2016-02-05 0:19 ` Bjorn Helgaas
2016-02-05 8:35 ` Jayachandran Chandrashekaran Nair
2016-02-05 9:47 ` Lorenzo Pieralisi [this message]
2016-02-05 23:26 ` Rafael J. Wysocki
2016-02-06 9:58 ` Jayachandran Chandrashekaran Nair
2016-02-08 11:27 ` Jayachandran Chandrashekaran Nair
2016-02-10 13:30 ` Lorenzo Pieralisi
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=20160205094740.GA31547@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jayachandran.chandrashekaran@broadcom.com \
--cc=jchandra@broadcom.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tn@semihalf.com \
--cc=xen-devel@lists.xenproject.org \
/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).