Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp245358ybl; Thu, 15 Aug 2019 16:34:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqzhBpTiJpZ1LXP6aRpIRL7GJ5mAf61TQluhuB9W5x0ow84T1Hn5Ni5F61iZDZZARBE9K29K X-Received: by 2002:a17:90a:21eb:: with SMTP id q98mr4323745pjc.23.1565912040544; Thu, 15 Aug 2019 16:34:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565912040; cv=none; d=google.com; s=arc-20160816; b=nASxJbdR/qJnGAEKsJzvIukH4SVVak91sph7rOFhBcy6UHMElRLDP0JRoUxqgcsXOp h0X3/R+cSeqg1L+zKw6+wFnW406OCFZm4iwj4FTcEovlFmJUBRt18SRkWhilaf6bzSv/ 74X9HCRmwHyAcexUmmteroRrknPFdvq4AvWKN1KUC4NUitdN9NSpzYksP+Rpwwjl6mUJ WG503P6G2JP1y2C33088owQ9WEcSlQayFmwwafaCMoIZHcjWcD3Vm/s66f8RinH+QC8t H2fCNs2cuzYxq5NHJJ3hFhsmncQwM78HIXkt1lx0Rap7LA/Y5nwnLDsWLJDdeAaUq/j/ aJMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=9F1gLLqJG9OfSgGg4BofqJKb0YiV8X3nV0lewrzt5iY=; b=kYb8MBwjEfg9aUReD5gRGw03rbFoyuTpfLmQv3j3fULP3Li1mkIZ/8FcUo905kWI9U rbEUuwpGOlGqhcTKbEjIxlSniOdnFKNkWXRn+E3V1gTkDPmCC+TaxsGUiFNzf9VGnycs IzehxEqMZxkkgCsFUMr2p3YxHOLbJzdF1EkvVaCGVEgnsAunIQr/FzJzPDm/E+C/OQiz cWUElU2Hq2bz+Dk4OcYzQy1rIRsgUcSnwmrE/TOB4Tg/whZN+QuOhztJUOYl9gwBjtu2 Sa/pn7M06o51G7Rp4jjZDWx9dC/bxaFf2SwSkUvgTRrZnfe+DbIvg4ZqCXi1AamCpmlA m8QQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=J7yaYGqL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y19si2815324pll.326.2019.08.15.16.33.42; Thu, 15 Aug 2019 16:34:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=J7yaYGqL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732948AbfHOU4V (ORCPT + 99 others); Thu, 15 Aug 2019 16:56:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:42144 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730540AbfHOU4V (ORCPT ); Thu, 15 Aug 2019 16:56:21 -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 4F84D2086C; Thu, 15 Aug 2019 20:56:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565902580; bh=CurYYhwg/rTAP0CdgcbXS3++QbH1EutUlsXldHCNbaA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=J7yaYGqLZ8WizZ5FBQ2faP59qa6jwrcpYkOF99kaTrn0FUVPA9SFsJFHb5tcdhetP k8tFlSqW3CmNBjFqtSY1zd7fVHqhMrNdOxBVKBORTm2ppqSDA21gdYovncrIWyTZH2 kMGxTokkljHjq/H1PZsLBeQycFPpztdYRc7fQ6Oc= Date: Thu, 15 Aug 2019 22:56:18 +0200 From: Greg KH To: Daniel Mack 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 Message-ID: <20190815205618.GA11877@kroah.com> References: <20190811110213.5537-1-daniel@zonque.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190811110213.5537-1-daniel@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 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