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>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Oleg Nesterov" <oleg@redhat.com>
Subject: [GIT PULL] PCI fixes for v6.14
Date: Fri, 14 Feb 2025 17:49:04 -0600 [thread overview]
Message-ID: <20250214234904.GA174406@bhelgaas> (raw)
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.14-fixes-3
for you to fetch changes up to 81f64e925c29fe6e99f04b131fac1935ac931e81:
PCI: Avoid FLR for Mediatek MT7922 WiFi (2025-02-13 08:36:54 -0600)
----------------------------------------------------------------
- Update a BUILD_BUG_ON() usage that works on current compilers, but breaks
compilation on gcc 5.3.1 (Alex Williamson)
- Avoid use of FLR for Mediatek MT7922 WiFi; the device previously worked
after a long timeout and fallback to SBR, but after a recent RRS change
it doesn't work at all after FLR (Bjorn Helgaas)
----------------------------------------------------------------
Alex Williamson (1):
PCI: Fix BUILD_BUG_ON usage for old gcc
Bjorn Helgaas (1):
PCI: Avoid FLR for Mediatek MT7922 WiFi
drivers/pci/probe.c | 5 +++--
drivers/pci/quirks.c | 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
next reply other threads:[~2025-02-14 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 23:49 Bjorn Helgaas [this message]
2025-02-15 0:53 ` [GIT PULL] PCI fixes for v6.14 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 19:46 Bjorn Helgaas
2025-02-06 23:12 ` 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=20250214234904.GA174406@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marmarek@invisiblethingslab.com \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.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