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 129E2C433FE for ; Thu, 5 May 2022 12:57:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378349AbiEENB0 (ORCPT ); Thu, 5 May 2022 09:01:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1378325AbiEENBY (ORCPT ); Thu, 5 May 2022 09:01:24 -0400 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA5B55418F for ; Thu, 5 May 2022 05:57:43 -0700 (PDT) Received: by mail-ej1-x632.google.com with SMTP id ks9so2148224ejb.2 for ; Thu, 05 May 2022 05:57:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RybWbrXcj8zBS10i0C/9NHfeL8tGwcNcqo6inv4EpAI=; b=d7ws1vmB8TNasv2lYZpKICd2vTQXUueLbTwFXYGVqHpQ8H7SyvH2fl6/g62DCgDWaA fRW66tJ5nWbqkYv2F+uwnoUBQ0VhC7V40TrefZW2K7wY5hhgHFI0bMpqYtJsxDlk/IP8 AQFbrHBEVLvgQHq3gyz3ga5LiF8TDzDBKFzBq/3CLCP+nEXz1UNTy7EM8Pj2M6D7/bXx rVmyxES41BJeedBgaQs82ycRHSuZpGNQHb+HIHtYs19eNWBu0xI6aA5uVIsoFPKxMdhv jcdEBeWv/1d59lQKC+eLFIb73JCKOYx1yiBelaxx/HkTPjtP+53zYjRczjThZJQLBaYP beUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RybWbrXcj8zBS10i0C/9NHfeL8tGwcNcqo6inv4EpAI=; b=h7/+niZzM1nz8Hv6Y2sSv3JKzuG6ZnL465cCb2DnrOSJOGb7n/Qqdi0qkVVL/nLzvz xdN+vz242voqikXpRlFBYu6pch/6pLnhLPM7Cwa7DWP9fvZUsSNrE6xOUoQc6NbF685+ hL6K7+0Eb8jvnSJfPU5ahMOohWPhdsqwVWzszJg0ZReBHi9FBpqQ2/BX0d8BNshDaaRD BPug3P9u2Z6T+7QufFBwrbFEuKXws+80Ew2SnwOeyQjwQjul+CCX4gdXne16TskwWvSS E/G2abSejtENy0SgwyGjKlLAY/lRRnT3yp0pMyBYp+L4FBuGuGPQ5ot38UaPQvMZzKU1 HyKg== X-Gm-Message-State: AOAM533cDqUx0EpcSHVa1RdR3d0HY5dXepjYUj8Ox0WIl/vOsQapd5BV qxg35ICoOnxBacc/mgiNiiwSkzSu13lx2udZQdfG3Q== X-Google-Smtp-Source: ABdhPJzm7DvuddhoB6IlDfOb7PG3Zm7dp7T7j+cXQJ/VMgHGfFkalZ86UDm1bktcuRSPyzrSERhqQrQnGfs2PDceCNc= X-Received: by 2002:a17:907:3e28:b0:6f4:3900:78f8 with SMTP id hp40-20020a1709073e2800b006f4390078f8mr21669903ejc.736.1651755462487; Thu, 05 May 2022 05:57:42 -0700 (PDT) MIME-Version: 1.0 References: <20220504144406.36744-1-jonathanh@nvidia.com> <6629e06d06f647923c04502ce3133f76@kernel.org> In-Reply-To: <6629e06d06f647923c04502ce3133f76@kernel.org> From: Bartosz Golaszewski Date: Thu, 5 May 2022 14:57:31 +0200 Message-ID: Subject: Re: [PATCH V2] gpio: max77620: Make the irqchip immutable To: Marc Zyngier Cc: Jon Hunter , Linus Walleij , "open list:GPIO SUBSYSTEM" , Linux Kernel Mailing List , linux-tegra@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Thu, May 5, 2022 at 2:54 PM Marc Zyngier wrote: > > On 2022-05-05 13:42, Bartosz Golaszewski wrote: > > On Wed, May 4, 2022 at 4:44 PM Jon Hunter wrote: > >> > >> Commit 6c846d026d49 ("gpio: Don't fiddle with irqchips marked as > >> immutable") added a warning to indicate if the gpiolib is altering the > >> internals of irqchips. Following this change the following warning is > >> now observed for the max77620 gpio driver ... > >> > >> WARNING KERN gpio gpiochip0: (max77620-gpio): not an immutable chip, > >> please consider fixing it! > >> > >> Fix the above warning by making the max77620 gpio driver immutable. > >> > >> Signed-off-by: Jon Hunter > >> --- > > > > Queued for fixes, thanks! > > You mean fixes for *5.19*, right? > Of course I did. 100%. And I'll stick to this version. :) (Thanks for the heads-up!) Bart