From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nikam.ms.mff.cuni.cz ([195.113.20.16]:49726 "EHLO nikam.ms.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728066AbeHLN3Z (ORCPT ); Sun, 12 Aug 2018 09:29:25 -0400 Date: Sun, 12 Aug 2018 12:51:46 +0200 From: Martin Mares To: Matthew Wilcox Cc: Logan Gunthorpe , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-doc@vger.kernel.org, Stephen Bates , Christoph Hellwig , Bjorn Helgaas , Jonathan Corbet , Ingo Molnar , Thomas Gleixner , "Paul E. McKenney" , Marc Zyngier , Kai-Heng Feng , Frederic Weisbecker , Dan Williams , =?utf-8?B?SsOpcsO0bWU=?= Glisse , Benjamin Herrenschmidt , Alex Williamson , Christian =?utf-8?B?S8O2bmln?= Subject: Re: lspci: Display path to device Message-ID: References: <20180717170204.30470-1-logang@deltatee.com> <20180717203900.GA1771@bombadil.infradead.org> <20180810145655.GA16533@bombadil.infradead.org> <20180812103133.GB2984@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20180812103133.GB2984@bombadil.infradead.org> Sender: linux-pci-owner@vger.kernel.org List-ID: Hello! > I agree it's more intuitive, but it's not the format that Logan's code > is expecting, so it's not as useful for my purposes. How about this? > > $ ./lspci -PF tests/fujitsu-p8010.lspci -s 1d:00.0 > 00:1e.0/03.0/00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01) > $ ./lspci -PPF tests/fujitsu-p8010.lspci -s 1d:00.0 > 00:1e.0/1c:03.0/1d:00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01) Yes, this looks fine. It is merged to master now and I will push a new release out of the door soon. Thanks! Martin