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>,
Lukas Wunner <lukas@wunner.de>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Borislav Petkov <bp@suse.de>
Subject: [GIT PULL] PCI fixes for v5.1
Date: Thu, 28 Mar 2019 14:03:40 -0500 [thread overview]
Message-ID: <20190328190340.GD24180@google.com> (raw)
PCI fixes:
- Clear level-triggered interrupts for the bandwidth notification
supported added for v5.1 (Alexandru Gagniuc)
- Clear bandwidth notification interrupts before enabling them (Lukas
Wunner)
- Report post-enumeration bandwidth changes only once for multi-function
devices (Lukas Wunner)
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.1-fixes-1
for you to fetch changes up to 0fa635aec9abd718bd18c0bda2261351a0811efc:
PCI/LINK: Deduplicate bandwidth reports for multi-function devices (2019-03-25 17:59:07 -0500)
----------------------------------------------------------------
pci-v5.1-fixes-1
----------------------------------------------------------------
Alexandru Gagniuc (1):
PCI/LINK: Supply IRQ handler so level-triggered IRQs are acked
Lukas Wunner (2):
PCI/LINK: Clear bandwidth notification interrupt before enabling it
PCI/LINK: Deduplicate bandwidth reports for multi-function devices
drivers/pci/pci.h | 1 +
drivers/pci/pcie/bw_notification.c | 23 +++++++++++++++++------
drivers/pci/probe.c | 2 +-
3 files changed, 19 insertions(+), 7 deletions(-)
next reply other threads:[~2019-03-28 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 19:03 Bjorn Helgaas [this message]
2019-03-28 21:15 ` [GIT PULL] PCI fixes for v5.1 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-04-12 15:38 Bjorn Helgaas
2019-04-13 22:00 ` pr-tracker-bot
2019-05-02 13:55 Bjorn Helgaas
2019-05-02 16:15 ` 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=20190328190340.GD24180@google.com \
--to=helgaas@kernel.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=mr.nuke.me@gmail.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 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.