From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BC24FC3A5A3 for ; Tue, 27 Aug 2019 17:04:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 90A9921883 for ; Tue, 27 Aug 2019 17:04:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566925490; bh=XeUdz62QOCJpL9O1N11O4eJhz/7iILY7JLWPy9nGNRo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=X9HDO5vqdLH1UNEuvPiyrlFRbe1eAzOINzmD+10WqNMZOh/WWxQ9zdBQilrZqfG30 ZB4xR0vnbCJ4BJOKf6xfHN99CJeVPRo74wFacBT1GkmwnfzUePHVDLSjSc7lWlOu/P 08Mk6uxUw7IZDg5wxob96zsovya/FFNtcMSe8tHA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730333AbfH0REt (ORCPT ); Tue, 27 Aug 2019 13:04:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:47694 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727807AbfH0REt (ORCPT ); Tue, 27 Aug 2019 13:04:49 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 302982184D; Tue, 27 Aug 2019 17:04:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566925488; bh=XeUdz62QOCJpL9O1N11O4eJhz/7iILY7JLWPy9nGNRo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WuXkd4wEUqFBqeJj/V6ZjioNe1M9rL5cnJrGFU/7m31OcEWeb+k1i/SkBWbTWRTec pym9Zae69TjiBa6itpx8NnNfXBipBt8PyxGCl7JVWBCs5BBnxokDf/wnDUxo3oSWPC nFSnat0K5JQrZNeho8SPt2JvvHfTKQkzoOMPKiA4= Date: Tue, 27 Aug 2019 19:04:46 +0200 From: Greg KH To: Daniel Mack Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] uio: uio_pdrv_genirq: Make UIO name controllable via DT node property Message-ID: <20190827170446.GA21369@kroah.com> References: <20190815212807.25058-1-daniel@zonque.org> <3f65e92e-350e-d414-75c4-8680932b39d1@zonque.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3f65e92e-350e-d414-75c4-8680932b39d1@zonque.org> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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