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: <20190827170446.GA21369@kroah.com>
Date:   Tue, 27 Aug 2019 19:04:46 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Daniel Mack <daniel@...que.org>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] uio: uio_pdrv_genirq: Make UIO name controllable
 via DT node property

On Tue, Aug 27, 2019 at 06:07:04PM +0200, Daniel Mack wrote:
> Hi Greg,
> 
> On 15/8/2019 11:28 PM, Daniel Mack wrote:
> > When probed via DT, the uio_pdrv_genirq driver currently uses the name
> > of the node and exposes that as name of the UIO device to userspace.
> > 
> > This doesn't work for systems where multiple nodes with the same name
> > (but different unit addresses) are present, or for systems where the
> > node names are auto-generated by a third-party tool.
> > 
> > This patch adds the possibility to read the UIO name from the optional
> > "linux,uio-name" property.
> 
> Any opinion on this one?

Sorry, it's in my "to review" queue, was traveling all last week and
it's really big now :(

it's not lost...

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ