Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752443AbdHBIc1 (ORCPT ); Wed, 2 Aug 2017 04:32:27 -0400 Received: from mail-oi0-f65.google.com ([209.85.218.65]:37873 "EHLO mail-oi0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751950AbdHBIcY (ORCPT ); Wed, 2 Aug 2017 04:32:24 -0400 MIME-Version: 1.0 In-Reply-To: <2153314.vmO4TSUiTO@ws-stein> References: <20170802075126.17637-1-brgl@bgdev.pl> <20170802075126.17637-5-brgl@bgdev.pl> <2153314.vmO4TSUiTO@ws-stein> From: Andy Shevchenko Date: Wed, 2 Aug 2017 11:32:23 +0300 Message-ID: Subject: Re: [PATCH 4/6] gpio: mxc: use devres for irq generic chip To: Alexander Stein Cc: Bartosz Golaszewski , Linus Walleij , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 492 Lines: 14 On Wed, Aug 2, 2017 at 11:09 AM, Alexander Stein wrote: > On Wednesday 02 August 2017 09:51:24, Bartosz Golaszewski wrote: >> Use resource managed variants of irq_alloc_generic_chip() and >> irq_setup_generic_chip(). > > Is this really useful for drivers which can only be built-in? But you still can unbind the driver and its ->remove() will be called (in case of no remove, devres still on the table), right? -- With Best Regards, Andy Shevchenko