From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bean Huo <huobean@gmail.com>,
Xiaowei Song <songxiaowei@hisilicon.com>,
Binghui Wang <wangbinghui@hisilicon.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Tom Joseph <tjoseph@cadence.com>
Subject: [GIT PULL] PCI fixes for v5.17
Date: Fri, 4 Feb 2022 15:30:34 -0600 [thread overview]
Message-ID: <20220204213034.GA217708@bhelgaas> (raw)
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.17-fixes-3
for you to fetch changes up to 7dd3876205df92e07d824fe2264b38e0b8a9eec1:
PCI: kirin: Add dev struct for of_device_get_match_data() (2022-02-04 15:14:26 -0600)
N.B. These have been in linux-next for a couple days as 71c96af28da5
("PCI: kirin: Add dev struct for of_device_get_match_data()"), but I
amended that commit to add the reporter's info to the commit log.
----------------------------------------------------------------
PCI fixes:
- Restructure j721e_pcie_probe() so we don't dereference a NULL pointer
(Bjorn Helgaas)
- Add a kirin_pcie_data struct to identify different Kirin variants to
fix probe failure for controllers with an internal PHY (Bjorn Helgaas)
----------------------------------------------------------------
Bjorn Helgaas (2):
PCI: j721e: Initialize pcie->cdns_pcie before using it
PCI: kirin: Add dev struct for of_device_get_match_data()
drivers/pci/controller/cadence/pci-j721e.c | 85 +++++++++++++++---------------
drivers/pci/controller/dwc/pcie-kirin.c | 31 ++++++-----
2 files changed, 60 insertions(+), 56 deletions(-)
next reply other threads:[~2022-02-04 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 21:30 Bjorn Helgaas [this message]
2022-02-04 23:29 ` [GIT PULL] PCI fixes for v5.17 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 19:56 Bjorn Helgaas
2022-02-24 19:56 ` Bjorn Helgaas
2022-02-24 21:40 ` pr-tracker-bot
2022-02-24 21:40 ` pr-tracker-bot
2022-02-11 20:40 Bjorn Helgaas
2022-02-11 21:36 ` pr-tracker-bot
2022-01-29 16:15 Bjorn Helgaas
2022-01-29 17:07 ` pr-tracker-bot
2022-01-20 20:48 Bjorn Helgaas
2022-01-21 7:38 ` pr-tracker-bot
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=20220204213034.GA217708@bhelgaas \
--to=helgaas@kernel.org \
--cc=christian.gmeiner@gmail.com \
--cc=huobean@gmail.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=songxiaowei@hisilicon.com \
--cc=tjoseph@cadence.com \
--cc=torvalds@linux-foundation.org \
--cc=wangbinghui@hisilicon.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.