linux-kernel - Re: [PATCH 0/4] PCI: pciehp cleanup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 18 Jun 2015 16:12:52 -0500
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Cc:	Rajat Jain <rajatja@...gle.com>, Yinghai Lu <yinghai@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] PCI: pciehp cleanup

On Thu, Jun 18, 2015 at 11:12 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> These patches don't *do* anything except get rid of some overly verbose
> debug logging and a bunch of boilerplate code by inlining trivial things.
>
> Unless I made a mistake, this should not change the way anything works at
> all, although I did change some of the message text.
>
> ---
>
> Bjorn Helgaas (4):
>       PCI: pciehp: Clean up debug logging
>       PCI: pciehp: Make queue_interrupt_event() void
>       PCI: pciehp: Rename queue_interrupt_event() to pciehp_queue_interrupt_event()
>       PCI: pciehp: Inline the "handle event" functions into the ISR
>
>
>  drivers/pci/hotplug/pciehp.h      |    6 -
>  drivers/pci/hotplug/pciehp_core.c |   37 +--------
>  drivers/pci/hotplug/pciehp_ctrl.c |  154 +++----------------------------------
>  drivers/pci/hotplug/pciehp_hpc.c  |   89 +++++++++------------
>  4 files changed, 53 insertions(+), 233 deletions(-)

I applied these to pci/hotplug for v4.2 with acks/reviewed-by from
Rajat and Yinghai.  Thanks for taking a look!

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/