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: Wed, 10 Feb 2016 13:30:37 +0000 [thread overview]
Message-ID: <20160210133037.GA25060@red-moon> (raw)
In-Reply-To: <CAKc_7PVNm7z8nv_+Tr9FYhrVAA+-vh4CDMB83WAyT8tdi+CHzA@mail.gmail.com>
On Mon, Feb 08, 2016 at 04:57:46PM +0530, Jayachandran Chandrashekaran Nair wrote:
> Lorenzo,
>
> On Fri, Feb 5, 2016 at 3:17 PM, Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > 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 ?
>
> This is getting ridiculous, I had replied to your earlier mails on why
> my patchset is NOT doing the exact same thing. I had also explained
> why helping was not feasible.
>
> The basic point again: I am trying to give a much simpler patchset
> to solve the same problem, I take it that you haven't reviewed my
> patchset before writing this mail. I would have appreciated
> a technical discussion rather than this pointless flamefest.
>
> If you have reviewed it, you can see that there are just 5 patches
> instead of 23, and that overall it is a much simpler approach.
Ok, let's make it constructive. I think there is part of your
implementation that definitely makes sense (in particular the way you
cleaned-up the x86 MCFG unadulterated mess - patch 1), I will ask
Tomasz to integrate it, please work together on this.
I have nothing against your patchset, my point is that we can't keep
reviewing and testing two series (and I mean on ARM64 AND x86), please
understand my point, it is very time consuming to understand the
differences and make sure we don't break x86 in the process and I would
have to ask you to add all the code that I already reviewed in Tomasz's
set, I just do not want to do that.
I will reply to Tomasz, let's work together to have a single final
implementation please, I do not think I am asking too much here and
yes, by integrating part of your code I think Tomasz's patchset is
ready to go, obviously subject to Bjorn's review and opinion.
Thanks,
Lorenzo
WARNING: multiple messages have this Message-ID (diff)
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 5/5] PCI: ACPI: Add a generic ACPI based host controller
Date: Wed, 10 Feb 2016 13:30:37 +0000 [thread overview]
Message-ID: <20160210133037.GA25060@red-moon> (raw)
In-Reply-To: <CAKc_7PVNm7z8nv_+Tr9FYhrVAA+-vh4CDMB83WAyT8tdi+CHzA@mail.gmail.com>
On Mon, Feb 08, 2016 at 04:57:46PM +0530, Jayachandran Chandrashekaran Nair wrote:
> Lorenzo,
>
> On Fri, Feb 5, 2016 at 3:17 PM, Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com> wrote:
> > 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 ?
>
> This is getting ridiculous, I had replied to your earlier mails on why
> my patchset is NOT doing the exact same thing. I had also explained
> why helping was not feasible.
>
> The basic point again: I am trying to give a much simpler patchset
> to solve the same problem, I take it that you haven't reviewed my
> patchset before writing this mail. I would have appreciated
> a technical discussion rather than this pointless flamefest.
>
> If you have reviewed it, you can see that there are just 5 patches
> instead of 23, and that overall it is a much simpler approach.
Ok, let's make it constructive. I think there is part of your
implementation that definitely makes sense (in particular the way you
cleaned-up the x86 MCFG unadulterated mess - patch 1), I will ask
Tomasz to integrate it, please work together on this.
I have nothing against your patchset, my point is that we can't keep
reviewing and testing two series (and I mean on ARM64 AND x86), please
understand my point, it is very time consuming to understand the
differences and make sure we don't break x86 in the process and I would
have to ask you to add all the code that I already reviewed in Tomasz's
set, I just do not want to do that.
I will reply to Tomasz, let's work together to have a single final
implementation please, I do not think I am asking too much here and
yes, by integrating part of your code I think Tomasz's patchset is
ready to go, obviously subject to Bjorn's review and opinion.
Thanks,
Lorenzo
next prev parent reply other threads:[~2016-02-10 13:30 UTC|newest]
Thread overview: 45+ 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 ` Jayachandran C
2016-01-29 9:05 ` 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 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` 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 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` 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 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` [PATCH v7 4/5] arm64: pci: Add ACPI support Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` [PATCH v7 5/5] PCI: ACPI: Add a generic ACPI based host controller Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-01-29 9:05 ` Jayachandran C
2016-02-05 0:19 ` Bjorn Helgaas
2016-02-05 0:19 ` Bjorn Helgaas
2016-02-05 8:35 ` Jayachandran Chandrashekaran Nair
2016-02-05 8:35 ` Jayachandran Chandrashekaran Nair
2016-02-05 8:35 ` Jayachandran Chandrashekaran Nair
2016-02-05 9:47 ` Lorenzo Pieralisi
2016-02-05 9:47 ` Lorenzo Pieralisi
2016-02-05 9:47 ` Lorenzo Pieralisi
2016-02-05 23:26 ` Rafael J. Wysocki
2016-02-05 23:26 ` Rafael J. Wysocki
2016-02-06 9:58 ` Jayachandran Chandrashekaran Nair
2016-02-06 9:58 ` Jayachandran Chandrashekaran Nair
2016-02-06 9:58 ` Jayachandran Chandrashekaran Nair
2016-02-05 23:26 ` Rafael J. Wysocki
2016-02-08 11:27 ` Jayachandran Chandrashekaran Nair
2016-02-08 11:27 ` Jayachandran Chandrashekaran Nair
2016-02-08 11:27 ` Jayachandran Chandrashekaran Nair
2016-02-10 13:30 ` Lorenzo Pieralisi
2016-02-10 13:30 ` Lorenzo Pieralisi [this message]
2016-02-10 13:30 ` Lorenzo Pieralisi
2016-02-05 8:35 ` Jayachandran Chandrashekaran Nair
2016-02-05 0:19 ` Bjorn Helgaas
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=20160210133037.GA25060@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.