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] [day] [month] [year] [list]
Message-Id: <163362056400.23598.4839753526203041343.b4-ty@arm.com>
Date:   Thu,  7 Oct 2021 16:29:38 +0100
From:   Lorenzo Pieralisi <lorenzo.pieralisi@....com>
To:     bhelgaas@...gle.com, robh@...nel.org,
        brookxu <brookxu.cn@...il.com>, jonathan.derrick@...el.com
Cc:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        linux-kernel@...r.kernel.org, helgaas@...nel.org,
        linux-pci@...r.kernel.org, kw@...ux.com
Subject: Re: [PATCH v4] PCI: vmd: Assign a number to each VMD controller

On Fri, 17 Sep 2021 21:13:24 +0800, brookxu wrote:
> From: Chunguang Xu <brookxu@...cent.com>
> 
> If the system has multiple VMD controllers, the driver does not assign
> a number to each controller, so when analyzing the interrupt through
> /proc/interrupts, the names of all controllers are the same, which is
> not very convenient for problem analysis. Here, try to assign a number
> to each VMD controller.
> 
> [...]

Applied to pci/vmd, thanks!

[1/1] PCI: vmd: Assign a number to each VMD controller
      https://git.kernel.org/lpieralisi/pci/c/42da7911b8

Thanks,
Lorenzo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ