All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Alexandru Gagniuc <mr.nuke.me@gmail.com>
Cc: linux-pci@vger.kernel.org, Austin Bolen <austin_bolen@dell.com>,
	Alexandru Gagniuc <alex_gagniuc@dellteam.com>,
	Keith Busch <keith.busch@intel.com>,
	Shyam Iyer <Shyam_Iyer@Dell.com>, Sinan Kaya <okaya@kernel.org>
Subject: [PATCH 0/2] Link bandwidth notification fixes
Date: Wed, 20 Mar 2019 12:05:30 +0100	[thread overview]
Message-ID: <cover.1553078908.git.lukas@wunner.de> (raw)

These two small patches fix issues that showed up on my laptop when
testing the new bandwidth notification port service.  It may be worth
applying them to 5.1 still.

They're intended to be applied on top of Alexandru's patch "Do not leave
interrupt handler NULL" (or an updated version thereof which moves the
call to pcie_update_link_speed() to pcie_bw_notification_irq() per my
suggestion).

Thanks,

Lukas

Lukas Wunner (2):
  PCI/LINK: bw_notification: Clear interrupt before enabling it
  PCI/LINK: bw_notification: Deduplicate reports for multi-function
    devices

 drivers/pci/pci.h                  | 1 +
 drivers/pci/pcie/bw_notification.c | 4 +++-
 drivers/pci/probe.c                | 2 +-
 3 files changed, 5 insertions(+), 2 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-03-20 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-20 11:05 Lukas Wunner [this message]
2019-03-20 11:05 ` [PATCH 2/2] PCI/LINK: bw_notification: Deduplicate reports for multi-function devices Lukas Wunner
2019-03-25 18:52   ` Alex_Gagniuc
2019-03-20 11:05 ` [PATCH 1/2] PCI/LINK: bw_notification: Clear interrupt before enabling it Lukas Wunner
2019-03-25 18:50   ` Alex_Gagniuc
2019-03-25 22:33 ` [PATCH 0/2] Link bandwidth notification fixes Bjorn Helgaas

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=cover.1553078908.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=Shyam_Iyer@Dell.com \
    --cc=alex_gagniuc@dellteam.com \
    --cc=austin_bolen@dell.com \
    --cc=helgaas@kernel.org \
    --cc=keith.busch@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mr.nuke.me@gmail.com \
    --cc=okaya@kernel.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.