From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Mack <daniel@zonque.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: uio_pdrv_genirq: Make UIO name controllable via DT node property
Date: Thu, 15 Aug 2019 22:56:18 +0200 [thread overview]
Message-ID: <20190815205618.GA11877@kroah.com> (raw)
In-Reply-To: <20190811110213.5537-1-daniel@zonque.org>
On Sun, Aug 11, 2019 at 01:02:13PM +0200, 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.
Does that need to be documented anywhere?
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-15 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 11:02 [PATCH] uio: uio_pdrv_genirq: Make UIO name controllable via DT node property Daniel Mack
2019-08-15 20:56 ` Greg KH [this message]
2019-08-15 21:27 ` Daniel Mack
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=20190815205618.GA11877@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox