public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
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" <mani@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
	"Liang Jie" <liangjie@lixiang.com>,
	"Drew Fustini" <fustini@kernel.org>,
	"David Gow" <davidgow@google.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>
Subject: [GIT PULL] PCI fixes for v6.19
Date: Fri, 16 Jan 2026 10:54:35 -0600	[thread overview]
Message-ID: <20260116165435.GA928390@bhelgaas> (raw)

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.19-fixes-3

for you to fetch changes up to 05f66cf5e7a5fc7c7227541f8a4a476037999916:

  PCI: Provide pci_free_irq_vectors() stub (2026-01-12 10:45:31 -0600)

----------------------------------------------------------------

- Add a pci_free_irq_vectors() stub to fix a build issue when CONFIG_PCI is
  not set (Boqun Feng)

----------------------------------------------------------------
Boqun Feng (1):
      PCI: Provide pci_free_irq_vectors() stub

 include/linux/pci.h | 4 ++++
 1 file changed, 4 insertions(+)

             reply	other threads:[~2026-01-16 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 16:54 Bjorn Helgaas [this message]
2026-01-16 23:42 ` [GIT PULL] PCI fixes for v6.19 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-01-23 18:06 Bjorn Helgaas
2026-01-23 21:24 ` pr-tracker-bot
2026-01-09 16:20 Bjorn Helgaas
2026-01-09 16:40 ` pr-tracker-bot
2025-12-11 18:49 Bjorn Helgaas
2025-12-13  4:42 ` 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=20260116165435.GA928390@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=davidgow@google.com \
    --cc=fujita.tomonori@gmail.com \
    --cc=fustini@kernel.org \
    --cc=joelagnelf@nvidia.com \
    --cc=kwilczynski@kernel.org \
    --cc=liangjie@lixiang.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mani@kernel.org \
    --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