From: Will Deacon <will@kernel.org>
To: Xuesong Chen <xuesong.chen@linux.alibaba.com>
Cc: helgaas@kernel.org, catalin.marinas@arm.com,
lorenzo.pieralisi@arm.com, james.morse@arm.com,
rafael@kernel.org, tony.luck@intel.com, bp@alien8.de,
mingo@kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering
Date: Mon, 1 Nov 2021 09:36:18 +0000 [thread overview]
Message-ID: <20211101093618.GA27400@willie-the-truck> (raw)
In-Reply-To: <e387413f-dbe8-e0f1-257b-141362d74e3a@linux.alibaba.com>
Hi,
On Mon, Nov 01, 2021 at 10:18:35AM +0800, Xuesong Chen wrote:
> How about the status of this series, it's really bad, bad and still bad... to wait long
> time for the final judgement, especially you take extremely serious to rework it round
> by round, finaly you receive nothing. Everyone's work should be repected!
I've trimmed the rest of your response as it wasn't especially constructive.
Please can you try to keep things civil, even when you're frustrated? It's
not very pleasant being on the end of a rant.
One likely explanation for you not getting a reply on your patches is that
I've discovered many of your emails have ended up in my spam, for some
reason. I'm using gmail for my inbox so, if Bjorn is doing that as well,
then there's a good chance he hasn't seen them either.
The other thing to keep in mind is that the 5.16 merge window opened today
and you posted the latest version of your patches on Wednesday. That doesn't
really leave enough time for the patches to be reviewed (noting that patch 3
is new in this version and the kernel build robot was still complaining on
Friday), queued and put into linux-next, so I would suspect that this series
is looking more like 5.17 material and therefore not a priority for
maintainers at the moment.
Your best is probably to post a v5, with the kbuild warnings addressed,
when -rc1 is released in a couple of weeks. I'm not sure how to fix the
spam issue though :(
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Xuesong Chen <xuesong.chen@linux.alibaba.com>
Cc: helgaas@kernel.org, catalin.marinas@arm.com,
lorenzo.pieralisi@arm.com, james.morse@arm.com,
rafael@kernel.org, tony.luck@intel.com, bp@alien8.de,
mingo@kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering
Date: Mon, 1 Nov 2021 09:36:18 +0000 [thread overview]
Message-ID: <20211101093618.GA27400@willie-the-truck> (raw)
In-Reply-To: <e387413f-dbe8-e0f1-257b-141362d74e3a@linux.alibaba.com>
Hi,
On Mon, Nov 01, 2021 at 10:18:35AM +0800, Xuesong Chen wrote:
> How about the status of this series, it's really bad, bad and still bad... to wait long
> time for the final judgement, especially you take extremely serious to rework it round
> by round, finaly you receive nothing. Everyone's work should be repected!
I've trimmed the rest of your response as it wasn't especially constructive.
Please can you try to keep things civil, even when you're frustrated? It's
not very pleasant being on the end of a rant.
One likely explanation for you not getting a reply on your patches is that
I've discovered many of your emails have ended up in my spam, for some
reason. I'm using gmail for my inbox so, if Bjorn is doing that as well,
then there's a good chance he hasn't seen them either.
The other thing to keep in mind is that the 5.16 merge window opened today
and you posted the latest version of your patches on Wednesday. That doesn't
really leave enough time for the patches to be reviewed (noting that patch 3
is new in this version and the kernel build robot was still complaining on
Friday), queued and put into linux-next, so I would suspect that this series
is looking more like 5.17 material and therefore not a priority for
maintainers at the moment.
Your best is probably to post a v5, with the kbuild warnings addressed,
when -rc1 is released in a couple of weeks. I'm not sure how to fix the
spam issue though :(
Will
next prev parent reply other threads:[~2021-11-01 9:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 4:49 [PATCH v3 0/2] PCI MCFG consolidation and APEI resource filterin Xuesong Chen
2021-10-19 4:49 ` Xuesong Chen
2021-10-19 15:12 ` Bjorn Helgaas
2021-10-19 15:12 ` Bjorn Helgaas
2021-10-20 2:28 ` Xuesong Chen
2021-10-20 2:28 ` Xuesong Chen
2021-10-27 8:10 ` [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering Xuesong Chen
2021-10-27 8:10 ` Xuesong Chen
2021-10-27 8:12 ` [PATCH v4 1/4] PCI: MCFG: Consolidate the separate PCI MCFG table entry list Xuesong Chen
2021-10-27 8:12 ` Xuesong Chen
2021-10-27 8:12 ` [PATCH v4 2/4] ACPI: APEI: Filter the PCI MCFG address with an arch-agnostic method Xuesong Chen
2021-10-27 8:12 ` Xuesong Chen
2021-10-27 8:13 ` [PATCH v4 3/4] ACPI: APEI: Reserve the MCFG address for quirk ECAM implementation Xuesong Chen
2021-10-27 8:13 ` Xuesong Chen
2021-10-27 22:46 ` kernel test robot
2021-10-27 22:46 ` kernel test robot
2021-10-27 22:46 ` kernel test robot
2021-11-01 17:15 ` Bjorn Helgaas
2021-11-01 17:15 ` Bjorn Helgaas
2021-11-04 2:30 ` [kbuild-all] " Rong Chen
2021-11-04 2:30 ` Rong Chen
2021-10-27 22:46 ` [RFC PATCH] ACPI: APEI: remove_quirk_mcfg_res() can be static kernel test robot
2021-10-28 4:13 ` [PATCH v4 3/4] ACPI: APEI: Reserve the MCFG address for quirk ECAM implementation kernel test robot
2021-10-29 12:38 ` kernel test robot
2021-10-27 8:13 ` [PATCH v4 4/4] PCI: MCFG: Add the MCFG entry parse log message Xuesong Chen
2021-10-27 8:13 ` Xuesong Chen
2021-11-01 2:18 ` [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering Xuesong Chen
2021-11-01 2:18 ` Xuesong Chen
2021-11-01 9:36 ` Will Deacon [this message]
2021-11-01 9:36 ` Will Deacon
2021-11-01 12:12 ` Xuesong Chen
2021-11-01 12:12 ` Xuesong Chen
2021-11-01 12:22 ` Borislav Petkov
2021-11-01 12:22 ` Borislav Petkov
2021-11-01 13:32 ` Xuesong Chen
2021-11-01 13:32 ` Xuesong Chen
2021-11-01 13:55 ` Borislav Petkov
2021-11-01 13:55 ` Borislav Petkov
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=20211101093618.GA27400@willie-the-truck \
--to=will@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=helgaas@kernel.org \
--cc=james.morse@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mingo@kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=xuesong.chen@linux.alibaba.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 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.