From: Bjorn Helgaas <helgaas@kernel.org>
To: Saheed Olayemi Bolarinwa <refactormyself@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/11 RFC] PCI: Remove "*val = 0" from pcie_capability_read_*()
Date: Thu, 9 Jul 2020 19:11:02 -0500 [thread overview]
Message-ID: <20200710001102.GA29833@bjorn-Precision-5520> (raw)
In-Reply-To: <20200706093121.9731-1-refactormyself@gmail.com>
The cc list is really screwed up. Here's what I got:
Cc: Bolarinwa Olayemi Saheed <refactormyself@gmail.com>,
bjorn@helgaas.com,
skhan@linuxfoundation.org,
linux-pci@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
Russell Currey <ruscur@russell.cc>,
Sam Bobroff <sbobroff@linux.ibm.com>,
"Oliver O'Halloran" <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown Lukas Wunner <lenb@kernel.orglukas@wunner.de>,
linux-acpi@vger.kernel.org,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
"Greg Kroah-Hartman linux-rdma @ vger . kernel . org" <gregkh@linuxfoundation.org>
The addresses for Len Brown and Lukas Wunner are corrupted, as is Greg
KH's. And my reply-all didn't work -- it *should* have copied this to
everybody in the list, but Mutt apparently couldn't interpret the cc
list at all, so it left the cc list of my reply empty.
I added linux-pci by hand just so this will show up on the list.
On Mon, Jul 06, 2020 at 11:31:10AM +0200, Saheed Olayemi Bolarinwa wrote:
> From: Bolarinwa Olayemi Saheed <refactormyself@gmail.com>
>
> *** BLURB HERE ***
This series isn't structured quite right. You should replace the
"BLURB HERE" above with an actual description of the series.
> Bolarinwa Olayemi Saheed (9):
> IB/hfi1: Confirm that pcie_capability_read_dword() is successful
> misc: rtsx: Confirm that pcie_capability_read_word() is successful
> PCI/AER: Use error return value from pcie_capability_read_*()
> PCI/ASPM: Use error return value from pcie_capability_read_*()
> PCI: pciehp: Fix wrong failure check on pcie_capability_read_*()
> PCI: pciehp: Prevent wrong failure check on pcie_capability_read_*()
> PCI: pciehp: Make "Power On" the default in pciehp_get_power_status()
> PCI/ACPI: Prevent wrong failure check on pcie_capability_read_*()
> PCI: Prevent wrong failure check on pcie_capability_read_*()
> PCI: Remove "*val = 0" fom pcie_capability_read_*()
And the subject claims 11 patches ("PATCH 0/11"), the header above
claims 9, the list actually contains 10, and only 8 seem to have made
it to the mailing list:
$ b4 am -om/ https://lore.kernel.org/r/20200706093121.9731-1-refactormyself@gmail.com
Looking up https://lore.kernel.org/r/20200706093121.9731-1-refactormyself%40gmail.com
Grabbing thread from lore.kernel.org/linux-kernel-mentees
Analyzing 9 messages in the thread
---
Thread incomplete, attempting to backfill
Grabbing thread from lore.kernel.org/linuxppc-dev
Grabbing thread from lore.kernel.org/lkml
Server returned an error: 404
Grabbing thread from lore.kernel.org/linux-acpi
Server returned an error: 404
Grabbing thread from lore.kernel.org/linux-pci
Server returned an error: 404
Grabbing thread from lore.kernel.org/linux-rdma
Server returned an error: 404
---
Writing m/20200706_refactormyself_pci_remove_val_0_from_pcie_capability_read.mbx
ERROR: missing [1/11]!
[PATCH 2/11 RFC] misc: rtsx: Confirm that pcie_capability_read_word() is successful
[PATCH 3/11 RFC] PCI: pciehp: Validate with the return value of pcie_capability_read_*()
[PATCH 4/11 RFC] PCI: pciehp: Validate with the return value of pcie_capability_read_*()
[PATCH 5/11 RFC] PCI: pciehp: Make "Power On" the default
ERROR: missing [6/11]!
[PATCH 7/11 RFC] PCI: Validate with the return value of pcie_capability_read_*()
[PATCH 8/11 RFC] PCI/PM: Use error return value from pcie_capability_read_*()
ERROR: missing [9/11]!
[PATCH 10/11 RFC] PCI/ASPM: Use error return value from pcie_capability_read_*()
[PATCH 11/11 RFC] PCI: Remove "*val = 0" from pcie_capability_read_*()
---
Total patches: 8
---
WARNING: Thread incomplete!
next prev parent reply other threads:[~2020-07-10 0:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200706093121.9731-1-refactormyself@gmail.com>
2020-07-06 9:31 ` [PATCH 3/11 RFC] PCI: pciehp: Validate with the return value of pcie_capability_read_*() Saheed Olayemi Bolarinwa
2020-07-06 9:31 ` [PATCH 4/11 " Saheed Olayemi Bolarinwa
2020-07-06 9:31 ` [PATCH 5/11 RFC] PCI: pciehp: Make "Power On" the default Saheed Olayemi Bolarinwa
2020-07-10 0:14 ` Bjorn Helgaas
2020-07-10 21:42 ` Saheed Bolarinwa
2020-07-06 9:31 ` [PATCH 7/11 RFC] PCI: Validate with the return value of pcie_capability_read_*() Saheed Olayemi Bolarinwa
2020-07-06 9:31 ` [PATCH 8/11 RFC] PCI/PM: Use error return value from pcie_capability_read_*() Saheed Olayemi Bolarinwa
2020-07-06 9:31 ` [PATCH 10/11 RFC] PCI/ASPM: " Saheed Olayemi Bolarinwa
2020-07-10 0:11 ` Bjorn Helgaas [this message]
2020-07-10 21:32 ` [PATCH 0/11 RFC] PCI: Remove "*val = 0" " Saheed Bolarinwa
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=20200710001102.GA29833@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=refactormyself@gmail.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;
as well as URLs for NNTP newsgroup(s).