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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1EA0FC433EF for ; Mon, 16 May 2022 17:23:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240933AbiEPRXD (ORCPT ); Mon, 16 May 2022 13:23:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344186AbiEPRXC (ORCPT ); Mon, 16 May 2022 13:23:02 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3DF5B366BC; Mon, 16 May 2022 10:23:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652721782; x=1684257782; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Z6LbUx/xGNKKivZxZ3fa2EeCKH12QDQRC8tGE+sR4uo=; b=NV4pL9QWrBVfmfr7C+7AJc91YfBGrYjuaQz1gGxhXEIrCG9ntJ985+bX hRZsczfA6u+3Gutr2mFTCHsyEEXiOkxEeNgKrwTju9IExUf9JZ0Qnra5O pJgfGh4L+rfFllST5gHR5YiQpmTYnHeoGc+Jvcb9HuBgzS6gcBo7Rijoq QncwmIFJovMwwCRJh0QuTh86GQjK+vfjEK9vMTq6lXbqpOpnhg0CjVYIY O+pRRWzem6YRKPcE00HuzJ90U3XLtmnoEWwJucjkxbIVGc+dyxpo+Qk+a +qUiwxyIBGVw0Hpr4nLyLYc/WS9ED+SWOExU86m3IJJ+gtAMsgStBksmV w==; X-IronPort-AV: E=McAfee;i="6400,9594,10349"; a="250803262" X-IronPort-AV: E=Sophos;i="5.91,230,1647327600"; d="scan'208";a="250803262" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 May 2022 10:23:00 -0700 X-IronPort-AV: E=Sophos;i="5.91,230,1647327600"; d="scan'208";a="522546587" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 May 2022 10:22:57 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1nqeQo-0006wp-CQ; Mon, 16 May 2022 20:22:54 +0300 Date: Mon, 16 May 2022 20:22:54 +0300 From: Andy Shevchenko To: Linus Walleij Cc: Marc Zyngier , Hans de Goede , linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Bartosz Golaszewski , Jonathan Corbet , Mika Westerberg , Andy Shevchenko Subject: Re: [PATCH v1 1/5] Documentation: gpio: Fix IRQ mask and unmask examples Message-ID: References: <20220512173921.8210-1-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Fri, May 13, 2022 at 10:54:46PM +0200, Linus Walleij wrote: > On Thu, May 12, 2022 at 7:52 PM Andy Shevchenko > wrote: > > > After switching to immutable IRQ chips for GPIO drivers the examples become > > uncompilable due to wrong IRQ API, i.e. irq_desc_get_handler_data() in use. > > Replace it with proper irq_data_get_irq_chip_data() call where it applies. > > > > Fixes: 5644b66a9c63 ("Documentation: Update the recommended pattern for GPIO irqchips") > > Signed-off-by: Andy Shevchenko > > Reviewed-by: Linus Walleij Entire series with the respective tags has been pushed to my review and testing queue, thanks! -- With Best Regards, Andy Shevchenko