From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937853AbdAEF0D (ORCPT ); Thu, 5 Jan 2017 00:26:03 -0500 Received: from verein.lst.de ([213.95.11.211]:58093 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S937837AbdAEFZt (ORCPT ); Thu, 5 Jan 2017 00:25:49 -0500 Date: Thu, 5 Jan 2017 06:25:46 +0100 From: Christoph Hellwig To: Jan Kiszka Cc: Andy Shevchenko , Christoph Hellwig , Greg Kroah-Hartman , Andy Shevchenko , "linux-serial@vger.kernel.org" , Linux Kernel Mailing List Subject: Re: [PATCH] serial: 8250_lpss: Release Quark MSI vectors on exit Message-ID: <20170105052546.GA10503@lst.de> References: <0250c46e-da6c-71f3-50ae-b7c17fd0bd2c@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 04, 2017 at 11:46:58PM +0100, Jan Kiszka wrote: > > I NAKed already third patch related to PCI managed resources (couple > > of those regarding to pci_irq_* API)/ > > > > Ah, there are resources that are managed without being allocated > explicitly that way. Hmm, not very intuitive. Are MSI / MSI-X vectors > the only such cases? MSI/MSI-X resources are not managed that way and an explicit call to pci_free_irq_vectors is required from the API standpoint. It might not actually free memory in many cases, but it still is a symmetric API.